Path: csiph.com!usenet.pasdenom.info!news.etla.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.004 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'python.': 0.02; 'subject:Python': 0.06; 'differently': 0.07; 'subject: [': 0.09; 'used)': 0.09; 'windows': 0.15; '"just"': 0.16; '16-bit': 0.16; 'behave': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'range,': 0.16; 'range.': 0.16; 'two.': 0.16; 'unexpectedly': 0.16; 'wrote:': 0.18; '(the': 0.22; 'creating': 0.23; 'unicode': 0.24; 'subject:/': 0.26; 'header:In-Reply-To:1': 0.27; 'correct': 0.29; 'am,': 0.29; 'characters': 0.30; 'message- id:@mail.gmail.com': 0.30; 'code': 0.31; '(since': 0.31; 'linux': 0.33; 'fri,': 0.33; 'received:209.85': 0.35; 'common': 0.35; 'received:google.com': 0.35; 'received:209': 0.37; 'being': 0.38; 'subject:]': 0.38; 'to:addr:python-list': 0.38; 'bad': 0.39; 'to:addr:python.org': 0.39; 'most': 0.60; 'range': 0.61; 'different': 0.65; 'mar': 0.68; 'covers': 0.68; 'subject:long': 0.84; '2013': 0.98 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=m4J7zDHburgUZxA1iMYHgKzObOA0rvj31fz/NEmNmrg=; b=TcpQq/csIUHvaLdiVPfb49tsjjcMDtbv6UIebnfXDgMgcElQuZDYWURSVo4FKqoVMj KURoUKeCisw1ciwbBWFhqTkPuUoTfy/5R+Odup2X4GLODefJ4fCov3ANeAYME9tuI/O2 ws0Y+XJC6ClGm4NHEDJtjsgYNPGa7tUS4i2kLLi/2N0OMyOODJ6AU+lrSnyyucE6xVyb g0mxQcPD+Oh5vtjz4SBaqNKzjRFD6/hJJiFYYrFuxsN1UYaBuogA/SDln8faBrErriGx SbI51b3MuOJ7Jk5yLx+ajzIswZZ+RX8/PM196Pj2D2qgqtE0FVPM4/95SdjVpsogNXh+ BOBw== MIME-Version: 1.0 X-Received: by 10.52.67.164 with SMTP id o4mr195551vdt.42.1364507136354; Thu, 28 Mar 2013 14:45:36 -0700 (PDT) In-Reply-To: References: <5153a12d$0$29998$c3e8da3$5496439d@news.astraweb.com> <987c4bd9-0e5e-4387-9c78-1075a77d3c47@c6g2000yqh.googlegroups.com> <7f993624-8105-4055-a268-3417e5fe21dc@g4g2000yqd.googlegroups.com> Date: Fri, 29 Mar 2013 08:45:36 +1100 Subject: Re: flaming vs accuracy [was Re: Performance of int/long in Python 3] From: Chris Angelico To: python-list@python.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 14 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1364507145 news.xs4all.nl 6869 [2001:888:2000:d::a6]:46040 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:42195 On Fri, Mar 29, 2013 at 7:26 AM, jmfauth wrote: > The wide build (I never used) is in my mind as correct as > the narrow build. It "just" covers a different range in unicode > (the whole range). Actually it does; it covers all of the Unicode range, by using (effectively) UTF-16. Characters that cannot be represented in one 16-bit number are represented in two. That's not "just" covering a different range. It's being buggy. And it's creating a way for code to unexpectedly behave fundamentally differently on Windows and Linux (since the most common builds for Windows were narrow and for Linux were wide). This is a Bad Thing for Python. ChrisA