From 270126b5d113f80029a47ad7e06138eb541b50d8 Mon Sep 17 00:00:00 2001 From: Brett Cannon Date: Sun, 9 Dec 2012 13:31:24 -0500 Subject: [PATCH] Fix some markup where the wrong text markup style was used for bold and italic. --- pep-0399.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pep-0399.txt b/pep-0399.txt index 29a6b0162..4ed73507d 100644 --- a/pep-0399.txt +++ b/pep-0399.txt @@ -16,7 +16,7 @@ Abstract The Python standard library under CPython contains various instances of modules implemented in both pure Python and C (either entirely or partially). This PEP requires that in these instances that the -C code *must* pass the test suite used for the pure Python code +C code **must** pass the test suite used for the pure Python code so as to act as much as a drop-in replacement as reasonably possible (C- and VM-specific tests are exempt). It is also required that new C-based modules lacking a pure Python equivalent implementation get @@ -41,12 +41,12 @@ this leads these other VMs to either re-implement the modules in pure Python or in the programming language used to implement the VM itself (e.g., in C# for IronPython). This duplication of effort between CPython, PyPy, Jython, and IronPython is extremely unfortunate as -implementing a module *at least* in pure Python would help mitigate +implementing a module **at least** in pure Python would help mitigate this duplicate effort. The purpose of this PEP is to minimize this duplicate effort by mandating that all new modules added to Python's standard library -*must* have a pure Python implementation _unless_ special dispensation +**must** have a pure Python implementation *unless* special dispensation is given. This makes sure that a module in the stdlib is available to all VMs and not just to CPython (pre-existing modules that do not meet this requirement are exempt, although there is nothing preventing