Word File Processing in Python(Python處理Word檔案)

embed嵌入(bed床,放入床上,嵌入鑽戒)

影片重點

Let's develop brains.

作文，在捷運讓座let給老弱婦孺。

yield (投降, 收益)

Yield seats to elderly

YTM=Yield to Maturity=到期收益率

nominal yield=coupon rate=票面利率

利用python編輯edit建立create word 檔案

Process 處理....procedure程序

SOP 

python命令,給文件新增加一個段落

document.add_paragraph('文字內容',格式)

網頁javascript命令

document.create_element('P');

維基百科python了解

Python was conceived [構想, concept觀念, cognitive psychology認知心理學]in the late 1980s^[42] by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands; it was conceived as a successor [繼任者] to the ABC programming language, which was inspired [啟發,提示] by SETL,^[43] capable of exception handling and interfacing with the Amoeba operating system.^[12] Python implementation began in December 1989.^[44] Van Rossum assumed sole responsibility for the project, as the lead developer, until 12 July 2018, when he announced his "permanent vacation" from responsibilities as Python's "benevolent dictator for life" (BDFL); this title was bestowed on him by the Python community to reflect his long-term commitment as the project's chief decision-maker.^[45] (He has since come out of retirement and is self-titled "BDFL-emeritus".) In January 2019, active Python core developers elected a five-member Steering Council to lead the project.^[46][47]

The name Python is said to derive from the British comedy series Monty Python's Flying Circus.^[48]

Python 2.0 was released on 16 October 2000, with many major new features such as list comprehensions, cycle-detecting garbage collection, reference counting, and Unicode support.^[49] Python 2.7's end-of-life was initially set for 2015, and then postponed to 2020 out of concern that a large body of existing code could not easily be forward-ported to Python 3.^[50][51] It no longer receives security patches or updates.^[52][53] While Python 2.7 and older versions are officially unsupported, a different unofficial Python implementation, PyPy, continues to support Python 2, i.e., "2.7.18+" (plus 3.10), with the plus signifying (at least some) "backported security updates".^[54]

Python 3.0 was released on 3 December 2008, with some new semantics and changed syntax. At least every Python release since (the now unsupported) 3.5 has added some syntax to the language; a few later releases have removed outdated modules and have changed semantics, at least in a minor way.

As of 12 March 2025, Python 3.13 is the latest stable release. This version currently receives full bug-fix and security updates, while Python 3.12—released in October 2023—will have active bug-fix support only until April 2025. Python 3.9^[55] is the oldest supported version of Python (albeit in the 'security support' phase), because Python 3.8 has become an end-of-life product.^[56][57] Starting with Python 3.13, this and later versions receive two years of full support (which has increased from one and a half years), followed by three years of security support; this is the same total duration of support as previously.

Security updates were expedited in 2021 and again twice in 2022. More issues were fixed in 2023 and in September 2024 (for Python versions 3.8.20 through 3.12.6)—all versions (including 2.7)^[58] had been insecure because of issues leading to possible remote code execution^[59] and web-cache poisoning.^[60]

Python 3.10 added the | union type operator^[61] and the match and case keywords (for structural pattern matching statements). Python 3.11 expanded exception handling functionality. Python 3.12 added the new keyword type. Notable changes from version 3.10 to 3.11 include increased program execution speed and improved error reporting.^[62] Python 3.11 is claimed to be 10%–60% faster than Python 3.10, and Python 3.12 increases by an additional 5% . Python 3.12 also includes improved error messages (again improved in 3.14) and many other changes.

Python 3.13 introduces more syntax for types; a new and improved interactive interpreter [互動的解譯器] (REPL), featuring multi-line editing and color support; an incremental garbage collector, which results in shorter pauses for collection in programs that have many objects, as well as increasing the improved speed in 3.11 and 3.12); an experimental just-in-time (JIT) compiler (such features, can/needs to be enabled specifically for the increase in speed);^[63] and an experimental free-threaded build mode, which disables the global interpreter lock (GIL), allowing threads to run more concurrently, as enabled inpython3.13t or python3.13t.exe.

Python 3.13 introduces some changes in behavior, i.e., new "well-defined semantics", fixing bugs, and removing many deprecated classes, functions and methods (as well as some of the Python/C API and outdated modules). "The old implementation of locals() and frame.f_locals was slow, inconsistent and buggy, and it had many corner cases and oddities. Code that works around those may need revising; code that uses locals() for simple templating or print debugging should continue to work correctly."^[64]

Python 3.13 introduces the experimental free-threaded build mode, which disables the Global Interpreter Lock (GIL); the GIL is a feature of CPython that previously prevented multiple threads from executing Python bytecode simultaneously. This optional build, introduced through PEP 703, enables better exploitation of multi-core CPUs. By allowing multiple threads to run Python code in parallel, the free-threaded mode addresses long-standing performance bottlenecks associated with the GIL. This change offers a new path for parallelism in Python, without resorting to multiprocessing or external concurrency frameworks.^[65]

Some additional standard-library modules will be removed in Python 3.15 or 3.16, as will be many deprecated classes, functions and methods.^[66][67]

Python 3.11 adds Sigstore digital verification signatures for all CPython artifacts (in addition to PGP). Because the use of PGP has been criticized by security practitioners, Python is transitioning to Sigstore exclusively and dropping PGP from 3.14.^[68]

Python 3.14 is now in the alpha 3 phase. With regard to possible change to annotations, "In Python 3.14, from __future__ import annotations will continue to work as it did before, converting annotations into strings."^[69]

Python Enhancement Proposal (PEP) 711 proposes PyBI—a standard format for distributing Python binaries.^[70]

Python 3.15 will "Make UTF-8 mode default";^[71] This mode is supported in all current Python versions, but it currently must be opted into. UTF-8 is already used by default on Windows (and other operating systems) for most purposes; an exception is opening files. Enabling UTF-8 also makes code fully cross-platform.

basel III

(二)使用外部信用評等之原則, p.28 1.對各類型債權，銀行一經選用某外部信用評等機構及其評等結果，應保持一致性使用；不得任意自不同外部信用評等機構之評等結果中選取對本身有利（cherry-pick）之評等，亦不得任意變動所使用之信用評等機構。(頁28) \footnote{CRE21.8.\label{CRE21.8} Banks must use the chosen ECAIs and their ratings consistently for all types of exposure where they have been recognised by their supervisor as an eligible ECAI, for both risk-weighting and risk management purposes. Banks are not allowed to “cherry-pick” the ratings provided by different ECAIs and to arbitrarily change the use of ECAIs.} 2.若銀行某一特定債權只有一項外部信用評等機構之評等，其評等結果應用於決定該暴險之風險權數。 3.若銀行某一特定債權有兩項外部信用評等機構之評等，且對應至不同之風險權數，基於穩健原則，應選用較低之評等結果，亦即應適用較高之風險權數。 4.若銀行某一特定債權有 3 個或以上外部信用評等機構之評等，分別對應於各自風險權數，銀行應從中篩選出風險權數最低之兩個評等，如兩個評等對應相同之風險權數，則應採用該風險權數；如果不同，則應採用兩者當中較高的風險權數。 5.無論銀行所採用發行人評等或特定發行評等，應考量該評等能反映銀行債權中之全部信用暴險。如銀行暴險若包括本金及利息，則單就本金之評等不得予以採用作為決定其風險權數之依據。 6.當未評等信用暴險係依據同一借戶類似暴險之評等以決定其風險權數時，其原則為外幣評等僅適用於外幣暴險，而針對本國幣評等時，只能適用於決定以本國幣計價債權之風險權數。 7.短期評等一般適用於特定發行所作之評等，即某一筆特定短期評等不能適用於同一借款人之其他短期暴險，且不得以短期評等決定未評等長期暴險之風險權數。短期評等只能適用於對銀行及企業之短期暴險。短期暴險之風險權數如下表所示： 信用評等 A-1/P-1 45 A-2/P-2 A-3/P-3 其他 風險權數 20% 50% 100% 150% 8.對集團企業內某一企業之外部信用評等，不得用以決定該集團企業內其他企業之風險權數。 9.原則上銀行應採用合格外部信用評等機構之主動評等原則，如銀行擬採用被動評等資料時46，應採一致性基礎評估（例如不得因被動評等較差，而改採用未評等風險權數）。 10.若銀行投資於具有發行評等之特定有價證券，則該暴險之風險權數將依發行評等來決定，若銀行投資於不具發行評等之有價證券時，則應遵循以下之一般性原則： (1)當借款人已發行之某債務工具有特定發行評等，而銀行之暴險並非投資於該債務工具，若銀行所投資債務工具之優先順位在各方面都等同或優於前述具特定發行評等之債務工具，則該債務工具之高品質信用評等（對應之風險權數低於