Path: csiph.com!usenet.pasdenom.info!gegeweb.org!usenet-fr.net!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path: <python-python-list@m.gmane.org>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.002
X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'subject:Python': 0.06; 'differently': 0.07; 'memory.': 0.07; "'a'": 0.09; 'encode': 0.09; 'indeed,': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'subject: [': 0.09; 'jan': 0.12; 'behave': 0.16; 'encodings': 0.16; 'expects': 0.16; 'range.': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'reedy': 0.16; 'subject: \n ': 0.16; 'wrote:': 0.18; 'header:User-Agent:1': 0.23; 'example.': 0.24; 'unicode': 0.24; '(or': 0.24; 'define': 0.26; 'recognized': 0.26; 'references': 0.26; 'subject:/': 0.26; 'header:X-Complaints- To:1': 0.27; 'header:In-Reply-To:1': 0.27; 'idea': 0.28; 'character': 0.29; 'once,': 0.31; 'supposed': 0.32; 'another': 0.32; 'subject:]': 0.38; 'to:addr:python-list': 0.38; 'pm,': 0.38; 'does': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'read': 0.60; 'entire': 0.61; 'range': 0.61; 'received:173': 0.61; 'act': 0.63; 'provide': 0.64; 'more': 0.64; 'different': 0.65; 'believe': 0.68; '4:26': 0.84; 'received:fios.verizon.net': 0.84; 'subject:long': 0.84; 'remember,': 0.93
X-Injected-Via-Gmane: http://gmane.org/
To: python-list@python.org
From: Terry Reedy <tjreedy@udel.edu>
Subject: Re: flaming vs accuracy [was Re: Performance of int/long in Python 3]
Date: Thu, 28 Mar 2013 19:12:07 -0400
References: <mailman.3703.1364248275.2939.python-list@python.org> <kit1kg$g2u$1@ger.gmane.org> <nad-98F0A4.17004226032013@news.gmane.org> <kitdqr$4m4$2@ger.gmane.org> <nad-8CB9C0.18315026032013@news.gmane.org> <mailman.3805.1364385073.2939.python-list@python.org> <5153a12d$0$29998$c3e8da3$5496439d@news.astraweb.com> <mailman.3845.1364441182.2939.python-list@python.org> <d2cc443a-e049-42ed-abc6-66b5ea600fe7@j1g2000pbq.googlegroups.com> <mailman.3860.1364451682.2939.python-list@python.org> <987c4bd9-0e5e-4387-9c78-1075a77d3c47@c6g2000yqh.googlegroups.com> <mailman.3868.1364466636.2939.python-list@python.org> <b3808ea9-03fa-4781-aefe-af428899ee9c@5g2000yqz.googlegroups.com> <mailman.3901.1364488470.2939.python-list@python.org> <7f993624-8105-4055-a268-3417e5fe21dc@g4g2000yqd.googlegroups.com> <mailman.3905.1364493306.2939.python-list@python.org> <e58e23e5-9af9-4baa-bf93-4383d3d490f8@k4g2000yqn.googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Gmane-NNTP-Posting-Host: pool-173-75-251-66.phlapa.fios.verizon.net
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
In-Reply-To: <e58e23e5-9af9-4baa-bf93-4383d3d490f8@k4g2000yqn.googlegroups.com>
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.3922.1364512357.2939.python-list@python.org>
Lines: 23
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1364512357 news.xs4all.nl 6842 [2001:888:2000:d::a6]:45876
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:42201

On 3/28/2013 4:26 PM, jmfauth wrote:

Please provide references for your assertions. I have read the unicode 
standard, parts more than once, and your assertions contradict my memory.

> Unicode does not stipulate, one has to cover the whole range.

I believe it does. As I remember, the recognized encodings all encode 
the entire unicode codepoint range

> Unicode expects that every character in a range behaves the same
> way.

I have no idea what you mean by 'same way'. Each codepoint is supposed 
to behave differently in some way. That is the reason for having 
multiple codepoints. One causes an 'a' to appear, another a 'b'. Indeed, 
the standard define multiple categories of codepoints and chars in 
different categories are supposed to act differently (or be treated 
differently). Glyphic chars versus control chars are one example.

-- 
Terry Jan Reedy