Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #68061
| Date | 2014-03-09 02:42 +0000 |
|---|---|
| From | MRAB <python@mrabarnett.plus.com> |
| Subject | Re: How is unicode implemented behind the scenes? |
| References | <CAGGBd_rSN1bMHkQYix8Lo0TfXi3_k+Q9nu25vMokR1+Eumf5Cg@mail.gmail.com> <531BD49C.4090602@mrabarnett.plus.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.7945.1394332967.18130.python-list@python.org> (permalink) |
On 2014-03-09 02:40, MRAB wrote:
> On 2014-03-09 02:08, Dan Stromberg wrote:
>> OK, I know that Unicode data is stored in an encoding on disk.
>>
>> But how is it stored in RAM?
>>
>> I realize I shouldn't write code that depends on any relevant
>> implementation details, but knowing some of the more common
>> implementation options would probably help build an intuition for
>> what's going on internally.
>>
>> I've heard that characters are no longer all c bytes wide internally,
>> so is it sometimes utf-8?
>>
> No.
>
> From Python 3.3, it's an array of 1, 2 or 4 bytes per codepoint.
>
> In Python terms:
>
> if all(c <= '\xFF' for c in string):
> use 1 byte per codepoint
> elif all(c <= '\xFFFF' for c in string):
> use 2 bytes per codepoint
> else:
> use 4 bytes per codepoint
>
Oops! That should, of course, be:
if all(c <= '\xFF' for c in string):
use 1 byte per codepoint
elif all(c <= '\uFFFF' for c in string):
use 2 bytes per codepoint
else:
use 4 bytes per codepoint
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: How is unicode implemented behind the scenes? MRAB <python@mrabarnett.plus.com> - 2014-03-09 02:42 +0000
csiph-web