Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path: <python-python-list@m.gmane.org>
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; 'received:134': 0.05; 'incompatible': 0.07; 'python': 0.09; 'confuse': 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; 'list)': 0.16; 'message- id:@dough.gmane.org': 0.16; 'received:80.91.229.3': 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; '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; '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; '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; 'header:Received:5': 0.40; 'companies': 0.60; 'other.': 0.64; 'making': 0.64; 'subject:there': 0.65; 'prohibited': 0.74; 'banned': 0.84; 'manual,': 0.84; 'mean.': 0.91
X-Injected-Via-Gmane: http://gmane.org/
To: python-list@python.org
From: Serhiy Storchaka <storchaka@gmail.com>
Subject: Re: Why has python3 been created as a seperate language where there is still python2.7 ?
Date: Thu, 28 Jun 2012 08:36:15 +0300
References: <1340509604.38915.YahooMailClassic@web164605.mail.gq1.yahoo.com> <mailman.1484.1340619449.4697.python-list@python.org> <mailman.1503.1340677684.4697.python-list@python.org> <4fe92df1$0$29978$c3e8da3$5496439d@news.astraweb.com> <CABicbJKUZbFFmeRYN+yOuup5qoiJauo2jMukTFSv-1ZApQydoQ@mail.gmail.com> <jsbl4q$v84$1@dough.gmane.org> <4FEADFB4.5090301@stackless.com> <CAPTjJmpHaX1b+aHiRJ_a-kCUs-PrVZa6DGAw0AxKQ_=qpXJD5w@mail.gmail.com> <jseqe0$7fs$1@dough.gmane.org> <jsflll$lfd$1@dough.gmane.org> <jsft47$h1k$1@dough.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Gmane-NNTP-Posting-Host: 134.249.194.132
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
In-Reply-To: <jsft47$h1k$1@dough.gmane.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 <python-list.python.org>
List-Unsubscribe: <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.1585.1340861756.4697.python-list@python.org>
Lines: 21
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1340861756 news.xs4all.nl 6907 [2001:888:2000:d::a6]:46504
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:24590

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.