Path: csiph.com!usenet.pasdenom.info!news.albasani.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!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.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'from:addr:yahoo.co.uk': 0.04; 'syntax': 0.04; 'subject:Python': 0.06; 'incompatible': 0.07; '2to3': 0.09; 'invalidate': 0.09; 'lawrence': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'python': 0.11; 'language.': 0.14; 'changes': 0.15; '"from': 0.16; '__future__': 0.16; 'did.': 0.16; 'make,': 0.16; 'porting': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'statements,': 0.16; 'valid.': 0.16; 'language': 0.16; 'wrote:': 0.18; 'app': 0.19; 'later': 0.20; '>>>': 0.22; 'import': 0.22; 'print': 0.22; 'header:User-Agent:1': 0.23; '2.x': 0.24; 'bytes': 0.24; 'skip': 0.24; 'fairly': 0.24; 'possibly': 0.26; 'header:X -Complaints-To:1': 0.27; 'header:In-Reply-To:1': 0.27; 'hosting': 0.29; 'code': 0.31; '2008,': 0.31; 'piece': 0.31; 'there.': 0.32; 'running': 0.33; 'standards': 0.33; 'actual': 0.34; 'problem': 0.35; 'basic': 0.35; 'but': 0.35; 'google': 0.35; '14,': 0.36; 'url:org': 0.36; 'example,': 0.37; 'january': 0.37; 'being': 0.38; 'others.': 0.38; 'whatever': 0.38; 'to:addr:python-list': 0.38; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'major': 0.40; 'first': 0.61; 'companies': 0.62; 'offer': 0.62; 'such': 0.63; 'our': 0.64; 'six': 0.68; 'future,': 0.83; '2.7.': 0.84; 'capability': 0.84; 'cobol': 0.84; 'email addr:aol.com': 0.96 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Mark Lawrence Subject: Re: Python 3.x adoption Date: Fri, 17 Jan 2014 22:51:24 +0000 References: <3f88a958-4f3f-476c-bc9f-1b38ac0d084b@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: host-78-147-23-219.as13285.net User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 In-Reply-To: <3f88a958-4f3f-476c-bc9f-1b38ac0d084b@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 41 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1389999104 news.xs4all.nl 2945 [2001:888:2000:d::a6]:52439 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:64201 On 17/01/2014 22:16, beliavsky@aol.com wrote: > On Tuesday, January 14, 2014 2:38:29 PM UTC-5, Skip Montanaro wrote: >>> What's the problem with Python 3.x? It was first released in 2008, but >> >>> web hosting companies still seem to offer Python 2.x rather. >> >>> >> >>> For example, Google App Engine only offers Python 2.7. >> >>> >> >>> What's wrong?... >> >> >> >> What makes you think anything's wrong? Major changes to any >> >> established piece of software takes a fairly long while to infiltrate. >> >> Lots of COBOL and Fortran 77 still running out there. > > I don't think the Fortran analogy is valid. > > Later Fortran standards did not invalidate basic syntax such as print statements, as Python 3 did. Python 2 and 3 are incompatible in ways that do not apply to Fortran standards pre- and post- F77. > A good choice to make, the capability to use "from __future__ import print_function", or whatever the actual thing is, has been available for years. 2to3 has been available for years, six was released at the end of June 2010 and there's now future, see http://python-future.org/ Admittedly there's a problem with the porting of code which mixes bytes and strings, but that's being addressed right now via PEPs 460, 461 and possibly others. -- My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language. Mark Lawrence