Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!xlned.com!feeder7.xlned.com!newsfeed.xs4all.nl!newsfeed4.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.016 X-Spam-Evidence: '*H*': 0.97; '*S*': 0.00; 'argument': 0.05; 'subject:Python': 0.06; 'plenty': 0.07; 'additionally': 0.09; 'moreover,': 0.09; 'pep': 0.09; 'release.': 0.09; 'python': 0.11; '2.7': 0.14; '24,': 0.16; '3.3,': 0.16; 'behave': 0.16; 'division,': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'imports': 0.16; 'merely': 0.16; 'of"': 0.16; 'subject:ever': 0.16; 'wrote:': 0.18; 'library': 0.18; 'thu,': 0.19; 'bytes': 0.24; 'unicode': 0.24; 'handling': 0.26; 'header :In-Reply-To:1': 0.27; 'on,': 0.29; 'ease': 0.30; 'list:': 0.30; 'strongly': 0.30; 'message-id:@mail.gmail.com': 0.30; 'along': 0.30; 'code': 0.31; '3.x': 0.31; 'probably': 0.32; 'stuff': 0.32; 'run': 0.32; 'subject:the': 0.34; 'but': 0.35; 'received:google.com': 0.35; 'add': 0.35; 'there': 0.35; 'version': 0.36; 'subject:?': 0.36; 'project': 0.37; 'performance': 0.37; 'problems': 0.38; 'to:addr:python-list': 0.38; 'pm,': 0.38; 'moving': 0.39; 'to:addr:python.org': 0.39; 'unable': 0.39; 'major': 0.40; 'even': 0.60; 'skip:u 10': 0.60; 'future': 0.60; "you're": 0.61; "you'll": 0.62; 'high': 0.63; 'places': 0.64; 'become': 0.64; 'more': 0.64; 'improvements': 0.68; '2.7.': 0.84; '3.4': 0.84; 'flame': 0.84; 'gap': 0.84; 'pain': 0.84; 'widen': 0.84; '2013': 0.98 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=9N9lMSVmDzv9RU6OgRIJ11tXskPOSvYXbCFl8Qg/MJI=; b=J4A1hP+p7ZIdKpUGpmBgRUiB1h9Ywn5u29h8X7+luO2JpZ7x6jECY0xEhDtvD9JjUY 65wN5g6885KBNr+8WT+qZuAqf1E/Inz/moX2RiRiBO+JcUlxJ/TxDp17kZUP5GcT79Iy uWvXgzoWQ7WOFlm0ktiwPIsb/opT3ExpBFgxOiH0r5rjVz3ayBUF1JiGXFFCu/hKmlnp VFLZz9VNIo+wK8VXamXpFbgNMAL1mTTryU8tO5XkIt8hBOO3vKwJPT6FPnsm5Nz7PJ04 crwCRdisEmCV9/rzmxPoq/3nRZMCQTocx3bqoQNUoa4yZYnywCAdKfr1dA+sZTaqkDAE qbRQ== MIME-Version: 1.0 X-Received: by 10.68.233.135 with SMTP id tw7mr1296173pbc.112.1382597192275; Wed, 23 Oct 2013 23:46:32 -0700 (PDT) In-Reply-To: <0bbec535-dba0-4fc0-960f-f4ac9c79e64c@googlegroups.com> References: <6e0bbc6b-9435-4a4b-8840-8a46cc4e0cc5@googlegroups.com> <0bbec535-dba0-4fc0-960f-f4ac9c79e64c@googlegroups.com> Date: Thu, 24 Oct 2013 17:46:32 +1100 Subject: Re: Will Python 3.x ever become the actual standard? 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: 35 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1382597201 news.xs4all.nl 15966 [2001:888:2000:d::a6]:39547 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:57415 On Thu, Oct 24, 2013 at 3:57 PM, Peter Cacioppi wrote: > Moreover, you get a lot of the good stuff with 2.7. Along with more library support. So the smart decision is to code your project 2.7, even though the best thing for Pythonistan would be for us all to voluntarily migrate to 3.x. I won't flame you, but I will disagree with you :) You may get "a lot of" the good stuff with 2.7, but there are plenty of things you won't get - and the gap will widen with every Python release. As of 3.3, you're missing out on, among other things: * PEP 393 strings - high performance and perfect Unicode handling * 'yield from' * Major improvements to 'import' * High performance 'decimal' When 3.4 comes out, add to the list: * enumerations * asyncio * Argument Clinic (introspection) When 3.5 comes out, your 2.7 program will additionally be unable to use: * Who knows? * But it'll be exciting. If you insist on not moving to 3.x, I strongly recommend some future imports - unicode_literals, division, print_function - to make your 2.7 program behave more like a 3.x one. That'll ease the pain of transition, though you'll still probably run into problems with unicode vs bytes in places where your code used to be oblivious... which means your code will become guaranteed-correct when you move to 3.x, where the 2.7 version was merely accidentally-correct. ChrisA