Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.freenet.ag!news2.euro.net!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.005 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'cpython': 0.05; 'subject:Python': 0.06; 'utf-8': 0.07; 'string': 0.09; 'correct,': 0.09; 'git': 0.09; 'pep': 0.09; 'subject: [': 0.09; 'wrong,': 0.09; 'python': 0.11; 'correctness': 0.16; 'correctness.': 0.16; 'fork': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'preserve': 0.16; 'preserving': 0.16; 'term.': 0.16; 'unicode,': 0.16; 'unicode.': 0.16; 'wrote:': 0.18; 'figures': 0.19; 'thu,': 0.19; 'solution.': 0.20; 'memory': 0.22; 'example': 0.22; '(by': 0.24; 'certainly': 0.24; 'unicode': 0.24; "haven't": 0.24; '(or': 0.24; 'sort': 0.25; 'post': 0.26; 'subject:/': 0.26; 'header:In-Reply-To:1': 0.27; 'point': 0.28; '[1]': 0.29; 'message-id:@mail.gmail.com': 0.30; "i'm": 0.30; 'code': 0.31; 'piece': 0.31; 'run': 0.32; 'received:209.85': 0.35; 'problem.': 0.35; 'received:google.com': 0.35; 'google': 0.35; 'there': 0.35; 'really': 0.36; 'done': 0.36; 'received:209': 0.37; 'performance': 0.37; 'branch': 0.38; 'subject:]': 0.38; 'to:addr :python-list': 0.38; 'pm,': 0.38; 'though,': 0.39; 'to:addr:python.org': 0.39; 'skip:u 10': 0.60; 'results.': 0.60; 'range': 0.61; "you're": 0.61; 'first': 0.61; 'kind': 0.63; 'maximum': 0.63; 'between': 0.67; 'mar': 0.68; 'wish': 0.70; 'funny': 0.74; 'obvious': 0.74; 'benchmark': 0.84; 'replicate': 0.84; 'subject:long': 0.84; 'understand,': 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=+i+6pywsLVJ3c2vVR9Ax+DtQSuHzm8h0z8d7TqTfHGM=; b=UYAY+kFyazKK0Ah7x+jmKQQduNyTRDH5FpfnKUJMSgqJmlwgQJ2PpZVivy6H7YzC8s nAbZLvuN+qEMXd5fSGGMGo31Ct9mpXPtnYohSdtm/9T1irxhsCavsv/JG+xTarDwULei S454QFj+0VvQ4jvo1pTkEvfPEeGL3dvozy3N7QRnV3y0MijutCn7oASg6RwGfP8JG5w2 8T+wO/CZ0ifEM9wmRXTlO+/fdVfCevQsBldaLDG1V24zq7IIbJqc49RaPtKhLQiNY2Zb LKA2v1+UkKE+pHnAu4FXWVAKIKuFgPNk9PkNUH3/Iv8QNcM5cx5ZazoL559FofhSAZ0p sHrA== MIME-Version: 1.0 X-Received: by 10.220.109.145 with SMTP id j17mr26274366vcp.34.1364466627919; Thu, 28 Mar 2013 03:30:27 -0700 (PDT) In-Reply-To: <987c4bd9-0e5e-4387-9c78-1075a77d3c47@c6g2000yqh.googlegroups.com> References: <0b779c80-4f50-4716-8c30-47755c15f304@m12g2000yqp.googlegroups.com> <5153a12d$0$29998$c3e8da3$5496439d@news.astraweb.com> <987c4bd9-0e5e-4387-9c78-1075a77d3c47@c6g2000yqh.googlegroups.com> Date: Thu, 28 Mar 2013 21:30:27 +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: 31 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1364466636 news.xs4all.nl 6874 [2001:888:2000:d::a6]:56938 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:42112 On Thu, Mar 28, 2013 at 8:03 PM, jmfauth wrote: > Example of a good Unicode understanding. > If you wish 1) to preserve memory, 2) to cover the whole range > of Unicode, 3) to keep maximum performance while preserving the > good work Unicode.org as done (normalization, sorting), there > is only one solution: utf-8. For this you have to understand, > what is really a "unicode transformation format". You really REALLY need to sort out in your head the difference between correctness and performance. I still haven't seen one single piece of evidence from you that Python 3.3 fails on any point of Unicode correctness. Covering the whole range of Unicode has never been a problem. In terms of memory usage and performance, though, there's one obvious solution. Fork CPython 3.3 (or the current branch head[1]), change the internal representation of a string to be UTF-8 (by the way, that's the official spelling), and run the string benchmarks. Then post your code and benchmark figures so other people can replicate your results. > Python has certainly and definitvely not "revolutionize" > Unicode. This is one place where you're actually correct, though, because PEP 393 isn't the first instance of this kind of format - Pike's had it for years. Funny though, I don't think that was your point :) [1] Apologies if my terminology is wrong, I'm a git user and did one quick Google search to see if hg uses the same term. ChrisA