PEP 538: Add missing words
This commit is contained in:
parent
481573aa27
commit
03b6c20d26
|
@ -178,10 +178,10 @@ solution:
|
||||||
|
|
||||||
After reviewing both PEPs, it became clear that they didn't actually conflict
|
After reviewing both PEPs, it became clear that they didn't actually conflict
|
||||||
at a technical level, and the proposal in PEP 540 offered a superior option in
|
at a technical level, and the proposal in PEP 540 offered a superior option in
|
||||||
cases where no suitable locale was available, as well offering a better
|
cases where no suitable locale was available, as well as offering a better
|
||||||
reference behaviour for platforms where the notion of a "locale encoding"
|
reference behaviour for platforms where the notion of a "locale encoding"
|
||||||
doesn't make sense (for example, embedded systems running MicroPython rather
|
doesn't make sense (for example, embedded systems running MicroPython rather
|
||||||
the CPython reference interpreter).
|
than the CPython reference interpreter).
|
||||||
|
|
||||||
As a result, this PEP was amended to specify PEP 540 as a pre-requisite, with
|
As a result, this PEP was amended to specify PEP 540 as a pre-requisite, with
|
||||||
the aim being to coerce other C/C++ components into behaving consistently with
|
the aim being to coerce other C/C++ components into behaving consistently with
|
||||||
|
|
Loading…
Reference in New Issue