On 9/8/2014 1:44 AM, Marko Rauhamaa wrote:
Chris Angelico <ros...@gmail.com>:
The original question was regarding storage - how PEP 393 says that
strings will be encoded in memory in any of three ways (Latin-1,
UCS-2/UTF-16, or UCS-4/UTF-32). But even in our world, that is not
what a string *is*, but only what it is made of.
I'm a bit surprised that kind of CPython implementation detail would go
into a PEP. I had thought PEPs codified Python independently of CPython.
There are multiple PEP that are not strictly about Python the language:
meta-peps, informational peps, and others about the cpython api,
implementation, and distribution issues. 393 is followed by
397 Python launcher for Windows Hammond, v. Löwis
http://legacy.python.org/dev/peps/
The PEP process is a tool for the core development team and the product
is documentation of decisions and actions thereby
But maybe CPython is to Python what England is to the UK: even the
government is having a hard time making a distinction.
We don't.
--
Terry Jan Reedy
--
https://mail.python.org/mailman/listinfo/python-list
