iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 538: Minor JVM/CLR related clarifications

This commit is contained in:
Nick Coghlan 2017-05-05 00:59:53 +10:00
parent c1642ea4a3
commit dc175c5902
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pep-0538.txt
View File

@ -180,7 +180,7 @@ solution:
arise between CPython and other locale-aware components running in the same
process and in subprocesses. This approach aims to make CPython behave less
like a locale-aware application, and more like locale-independent language
runtimes like the JVM, .NET CLR, Go, Node.js, and Rust
runtimes like those for Go, Node.js (V8), and Rust
* this PEP proposes to override the legacy C locale with a more recently
defined locale that uses UTF-8 as its default text encoding. This means that
the text encoding override will apply not only to CPython, but also to any
@ -545,7 +545,7 @@ assumes UTF-8 by default (a behaviour inherited from the V8 JavaScript engine)
and requires custom build settings to indicate it should use the system
locale settings for locale-aware operations. Both the JVM and the .NET CLR
use UTF-16-LE as their primary encoding for passing text between applications
and the underlying platform.
and the application runtime (i.e. the JVM/CLR, not the host operating system).
The challenge for CPython has been the fact that in addition to being used for
network service development, it is also extensively used as an embedded