Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!ecngs!feeder2.ecngs.de!newsfeed.freenet.ag!news2.euro.net!newsfeed.xs4all.nl!newsfeed6.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; 'incompatible': 0.07; 'python': 0.09; '2to3': 0.09; 'confuse': 0.09; 'patch.': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'subject:Why': 0.09; 'subject:language': 0.09; 'subject:still': 0.09; 'terry': 0.09; 'decent': 0.16; 'deprecate': 0.16; 'fixer': 0.16; 'from:addr:behnel.de': 0.16; 'from:addr:stefan_ml': 0.16; 'from:name:stefan behnel': 0.16; 'list)': 0.16; 'message- id:@dough.gmane.org': 0.16; 'received:80.91.229.3': 0.16; 'received:mnet-online.de': 0.16; 'received:plane.gmane.org': 0.16; 'reedy': 0.16; 'society.': 0.16; 'subject: \n ': 0.16; 'subject:created': 0.16; 'subject:python2.7': 0.16; 'subject:python3': 0.16; 'subject:seperate': 0.16; 'subject:where': 0.16; 'wrote:': 0.17; 'stefan': 0.17; 'code,': 0.18; 'supposed': 0.21; 'features,': 0.22; 'feature': 0.24; 'least': 0.25; 'header:In-Reply-To:1': 0.25; 'header:User- Agent:1': 0.26; 'coding': 0.27; '(such': 0.27; 'authors': 0.27; 'strongly': 0.27; 'header:X-Complaints-To:1': 0.28; 'bad.': 0.29; 'maintenance,': 0.29; 'style.': 0.29; 'books': 0.30; 'subject: ?': 0.30; 'code': 0.31; 'rid': 0.33; 'to:addr:python-list': 0.33; 'themselves': 0.33; 'another': 0.33; 'next': 0.35; 'received:org': 0.36; 'but': 0.36; 'actions': 0.36; 'be.': 0.36; 'two': 0.37; 'subject:: ': 0.38; 'to:addr:python.org': 0.39; 'release': 0.39; 'header:Received:5': 0.40; 'your': 0.60; 'companies': 0.60; 'free': 0.61; 'back': 0.62; 'other.': 0.64; 'making': 0.64; 'subject:there': 0.65; 'prohibited': 0.74; 'banned': 0.84; 'manual,': 0.84; 'received:88.217': 0.84; 'mean.': 0.91 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Stefan Behnel Subject: Re: Why has python3 been created as a seperate language where there is still python2.7 ? Date: Thu, 28 Jun 2012 07:47:24 +0200 References: <1340509604.38915.YahooMailClassic@web164605.mail.gq1.yahoo.com> <4fe92df1$0$29978$c3e8da3$5496439d@news.astraweb.com> <4FEADFB4.5090301@stackless.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: ppp-88-217-77-110.dynamic.mnet-online.de User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 In-Reply-To: X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 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: 28 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1340862465 news.xs4all.nl 6881 [2001:888:2000:d::a6]:49273 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:24591 Serhiy Storchaka, 28.06.2012 07:36: > On 28.06.12 00:14, Terry Reedy wrote: >> Another prediction: people who code Python without reading the manual, >> at least not for new features, will learn about 'u' somehow (such as by >> reading this list) and may do either of the following, both of which are >> bad. >> >> 1. They will confuse themselves by thinking that 'u' actually means >> somethings. They may then confuse others by writing about its supposed >> meaning. This might get amusing. >> >> 2. They will use 'u' in Python 3 only code, thereby making it >> incompatible with 3.2-, even if it otherwise would not be. >> >> These two actions will reinforce each other. > > Yes, this is what I mean. I can even make a prediction: in just 5 years, as > this feature would be banned in a decent society. The authors of the books > will be strongly advise not to use it, and in software companies 'u' will > be prohibited in coding style. But get rid of this will be difficult. Once Py2.7 is out of maintenance, we can deprecate that feature in one release and start warning about it in the next one. You're then free to use the corresponding 2to3 fixer to get it back out of your code with a single patch. Stefan