Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!xlned.com!feeder5.xlned.com!newsfeed.xs4all.nl!newsfeed2.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.002 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'pycon': 0.01; '16,': 0.03; 'subject:Python': 0.06; 'lawrence': 0.09; 'rossum': 0.09; 'strings.': 0.09; 'cc:addr:python-list': 0.11; 'python': 0.11; 'missed': 0.12; '>>': 0.16; '*do': 0.16; '10+': 0.16; 'fine.': 0.16; 'folding.': 0.16; 'unchanged': 0.16; 'pushed': 0.16; 'wrote:': 0.18; '(not': 0.18; 'wed,': 0.18; 'bangalore': 0.19; '>>>': 0.22; 'import': 0.22; 'email addr:gmail.com>': 0.22; 'cc:addr:python.org': 0.22; '>>>': 0.24; '2.x': 0.24; 'bytes': 0.24; 'text,': 0.24; 'unicode': 0.24; 'question': 0.24; 'cc:2**0': 0.24; "i've": 0.25; '>': 0.26; '15,': 0.26; 'changes,': 0.26; 'supported': 0.26; 'van': 0.27; 'header:In- Reply-To:1': 0.27; 'fixed': 0.29; 'chris': 0.29; 'feature': 0.29; 'am,': 0.29; 'message-id:@mail.gmail.com': 0.30; 'url:mailman': 0.30; '3.x': 0.31; 'though.': 0.31; 'url:python': 0.33; 'skip:# 10': 0.33; 'comment': 0.34; 'but': 0.35; 'received:google.com': 0.35; 'really': 0.36; 'introducing': 0.36; 'url:listinfo': 0.36; "didn't": 0.36; 'url:org': 0.36; 'skip:& 10': 0.38; 'pm,': 0.38; 'anything': 0.39; 'does': 0.39; 'support,': 0.39; 'url:mail': 0.40; 'how': 0.40; 'read': 0.60; 'tell': 0.60; 'between': 0.67; 'jul': 0.74; 'saw': 0.77; '2015': 0.84; 'distinguish': 0.84; 'hanging': 0.84; '2020': 0.91; 'mean.': 0.91; 'to:none': 0.92 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:cc :content-type; bh=8lBbrkUkdji++8v6nIhhgWMGWlax0JeQy6XsQJ8wpHE=; b=rKLWi+84CHSinC8F/shk0PIUKaacuPM3SmdvYYRLHFAac4gr5p4O/V6CF1XjnDGtqM rLju5LDMh/EKwaNUjh6+GHKL2qvxiRIoT2WfDEl0vkZLRTtdaUsoqXwrISriGstbSpKL k6LPxUjcYidPWXnKXSGvInbZ8GsmgU+wry9oTGOlqtdDmtSKmDkkT255Cyyy2dx7BIAf HSLJVx31qj9GQNWoBNGemmx/PX0KoylckptC4rJn22fFgThReDO0DUJjPIeRSLNy/ezY e2+hpH+NSU0C0CBkx5UGUwaQiY5uXLhU1UR8IJgC95een9Tzz3OPWhczxQqCpnb7NM3y lUew== X-Received: by 10.112.157.68 with SMTP id wk4mr3934427lbb.85.1405460283249; Tue, 15 Jul 2014 14:38:03 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <57ajo9poljjre4c4ig0n0ss8kph8k78lp0@4ax.com> <5389cb53$0$29978$c3e8da3$5496439d@news.astraweb.com> <99b7b2a2-7521-42d7-a5a0-1a35d4d5b922@googlegroups.com> <53C4A454.9010600@gmail.com> <87zjga4j4v.fsf@elektro.pacujo.net> From: Abhiram R Date: Wed, 16 Jul 2014 03:07:23 +0530 Subject: Re: Python 3 is killing Python Cc: "comp.lang.python" Content-Type: multipart/alternative; boundary=001a11c2ae0eeddc5804fe42385c 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: 161 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1405460291 news.xs4all.nl 2830 [2001:888:2000:d::a6]:48226 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:74509 --001a11c2ae0eeddc5804fe42385c Content-Type: text/plain; charset=UTF-8 Annd I just saw that the lifetime has been pushed up to 2020 :) #SelfCorrected On Wed, Jul 16, 2014 at 3:05 AM, Abhiram R wrote: > Umm..Guido Van Rossum said in Pycon 2014 that Py 2.x would be supported > only until 2015 :-| So...you know.. you have like an year before you *do *have > to migrate to 3.x . > > > On Wed, Jul 16, 2014 at 2:17 AM, Devin Jeanpierre > wrote: > >> On Tue, Jul 15, 2014 at 1:24 PM, Mark Lawrence >> wrote: >> > On 15/07/2014 18:38, Marko Rauhamaa wrote: >> >> >> >> Chris Angelico : >> >> >> >>> Fine. Tell me how you would go about adding true Unicode support to >> >>> Python 2.7, while still having it able to import an unchanged program. >> >>> Trick question - it's fundamentally impossible, because an unchanged >> >>> program will not distinguish between bytes and text, but true Unicode >> >>> support requires that they be distinguished. >> >> >> >> >> >> Python 2 has always had unicode strings and [byte] strings. They were >> >> always clearly distinguished. You really didn't have to change anything >> >> for "true Unicode support". >> >> >> > >> > That is the funniest tongue in cheek comment I've read in the 10+ years >> > I''ve been hanging around here. It was tongue in cheek, wasn't it? >> >> What isn't "true" about Python 2.x's unicode support? The only feature >> I ever missed was case folding. (Not that 3.x does much better at that... >> :) >> >> The stdlib had poor unicode support, if that's what you mean. That >> could've been fixed without introducing backwards-incompatible >> changes, though. >> >> -- Devin >> -- >> https://mail.python.org/mailman/listinfo/python-list >> > > > > -- > Abhiram.R > M.Tech CSE (Sem 3) > RVCE > Bangalore > -- Abhiram.R M.Tech CSE (Sem 3) RVCE Bangalore --001a11c2ae0eeddc5804fe42385c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Annd I just saw that the lifetime has been pushed up to 2020 :) #Sel= fCorrected


On Wed, Jul 16, 2014 at 3:05 AM, Abhiram R <abhi.darkness@gmail.com<= /a>> wrote:
Umm..Guido Van Rossum said in Pycon 2014 that Py 2.x would be suppor= ted only until 2015 :-| So...you know.. you have like an year before you do have to migrate to 3.x .=C2=A0


On Wed, Jul 16, 2014 at 2:17 AM, Devin Jeanpierre <j= eanpierreda@gmail.com> wrote:
On Tue, Jul 15, 2014 at 1:24 PM, Mark L= awrence <br= eamoreboy@yahoo.co.uk> wrote:
> On 15/07/2014 18:38, Marko Rauhamaa wrote:
>>
>> Chris Angelico <rosuav@gmail.com>:
>>
>>> Fine. Tell me how you would go about adding true Unicode suppo= rt to
>>> Python 2.7, while still having it able to import an unchanged = program.
>>> Trick question - it's fundamentally impossible, because an= unchanged
>>> program will not distinguish between bytes and text, but true = Unicode
>>> support requires that they be distinguished.
>>
>>
>> Python 2 has always had unicode strings and [byte] strings. They w= ere
>> always clearly distinguished. You really didn't have to change= anything
>> for "true Unicode support".
>>
>
> That is the funniest tongue in cheek comment I've read in the 10+ = years
> I''ve been hanging around here. =C2=A0It was tongue in cheek, = wasn't it?

What isn't "true" about Python 2.x's unicode suppor= t? The only feature
I ever missed was case folding. (Not that 3.x does much better at that... := )

The stdlib had poor unicode support, if that's what you mean. That
could've been fixed without introducing backwards-incompatible
changes, though.

-- Devin
--
https://mail.python.org/mailman/listinfo/python-list



--
Abhiram.R
M.Tech CSE (Sem 3)
RVCE
Bangalore=C2=A0



--
Abhiram.R
M.Tech CSE (Sem 3)
RVCE
Bangalore=C2=A0
--001a11c2ae0eeddc5804fe42385c--