Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!ecngs!feeder2.ecngs.de!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.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'encoded': 0.05; 'incompatible': 0.07; 'python': 0.09; '2to3': 0.09; 'confuse': 0.09; 'patch.': 0.09; 'subject:Why': 0.09; 'subject:language': 0.09; 'subject:still': 0.09; 'terry': 0.09; 'to:addr:comp.lang.python': 0.09; 'unicode,': 0.09; 'cc:addr :python-list': 0.10; 'decent': 0.16; 'deprecate': 0.16; 'fixer': 0.16; 'list)': 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; 'cc:2**0': 0.23; 'cc:no real name:2**0': 0.24; 'feature': 0.24; 'least': 0.25; 'cc:addr:python.org': 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; 'argue': 0.29; 'bad.': 0.29; 'maintenance,': 0.29; 'style.': 0.29; 'books': 0.30; 'subject: ?': 0.30; 'thursday,': 0.30; 'code': 0.31; 'rid': 0.33; 'themselves': 0.33; 'another': 0.33; 'received:google.com': 0.34; 'received:209.85': 0.35; 'next': 0.35; 'but': 0.36; 'actions': 0.36; 'be.': 0.36; 'two': 0.37; 'received:209': 0.37; 'subject:: ': 0.38; 'release': 0.39; 'your': 0.60; 'from:no real name:2**0': 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; 'mean.': 0.91 Newsgroups: comp.lang.python Date: Thu, 28 Jun 2012 02:34:41 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=62.203.98.125; posting-account=ung4FAoAAAC46zhHJ0Nsnuox7M5gDvs_ References: <1340509604.38915.YahooMailClassic@web164605.mail.gq1.yahoo.com> <4fe92df1$0$29978$c3e8da3$5496439d@news.astraweb.com> <4FEADFB4.5090301@stackless.com> User-Agent: G2/1.0 X-Google-Web-Client: true X-Google-IP: 62.203.98.125 MIME-Version: 1.0 Subject: Re: Why has python3 been created as a seperate language where there is still python2.7 ? From: wxjmfauth@gmail.com To: comp.lang.python@googlegroups.com Content-Type: text/plain; charset=ISO-8859-1 Cc: python-list@python.org 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: , Message-ID: Lines: 37 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1340876092 news.xs4all.nl 6849 [2001:888:2000:d::a6]:54851 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:24599 On Thursday, June 28, 2012 7:47:24 AM UTC+2, Stefan Behnel wrote: > 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 On the other side, one can argue this (elegancy): b'a serie of bytes' u'a unicode, a serie of code points' 'python2? str? python3? encoded _unicode?' jmf