Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-March/117391.html below:

[Python-Dev] PEP-393/PEP-3118: unicode format specifiers

• Previous message: [Python-Dev] PEP-393/PEP-3118: unicode format specifiers
• Next message: [Python-Dev] Adding a builtins parameter to eval(), exec() and __import__().
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, Mar 7, 2012 at 8:50 PM, Stefan Krah <stefan at bytereef.org> wrote:
> *If* the arrays that Victor mentioned give one character per array location,
> then memoryview(str) could be used for zero-copy slicing etc.

A slight tangent, but it's worth trying to stick to the "code point"
term when talking about what Unicode strings contain. Even in UCS4,
full characters may be expressed as multiple code points (to be
honest, I still don't understand exactly how code points are composed
into graphemes and characters and mapped to glyphs for display, I just
know the mapping is a lot more complicated than the one-to-one implied
by referring to code points as characters).

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

• Previous message: [Python-Dev] PEP-393/PEP-3118: unicode format specifiers
• Next message: [Python-Dev] Adding a builtins parameter to eval(), exec() and __import__().
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4