Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <laf9gn$le8$1@ger.gmane.org>
References: <lablra$1mc$2@ger.gmane.org> <201401060932.35410.gheskett@wdtv.com> <laf2qm$4ep$1@ger.gmane.org> <201401061617.06746.gheskett@wdtv.com> <laf7fu$se5$1@ger.gmane.org> <laf7ut$1be$2@ger.gmane.org> <laf9gn$le8$1@ger.gmane.org>
Date: Mon, 6 Jan 2014 22:41:26 +0000
Subject: Re: "More About Unicode in Python 2 and 3"
From: Nicholas Cole <nicholas.cole@gmail.com>
To: Python <python-list@python.org>
Content-Type: multipart/alternative; boundary=001a1132f112c28f7304ef54f5b6
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.5080.1389048129.18130.python-list@python.org>
Lines: 99
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:63362

--001a1132f112c28f7304ef54f5b6
Content-Type: text/plain; charset=ISO-8859-1

I hardly know which of the various threads on this topic to reply to!

No one is taking Python 2.7 away from anyone.  It is going to be on the net
for years to come.  Goodness! I expect if I wanted to go and download
Python 1.5 I could find it easily enough.

Like everyone else, when Python 3 came out I was nervous.  A lot of my code
broke - but it broke for a good reason.  I had been being cavalier about
strings and ASCII and bytes.  A lot of my code was working by accident
rather than by design, or because my users had never fed it anything that
would make it fall over.  Of course, my first reaction was a defensive one,
but once I had got over that and got my head around Python 3's view of the
world, I was pleased I had.  I find writing in Python 3 leads to more
robust code.  I like the way it forces me to do the right thing, and I like
the way it raises errors if I try to get away with something I shouldn't.
Going back to Python 2 now feels a bit like stepping back to the seductive
and permissive hell of PHP in some ways!  If I could be sure that I was
coding just for me and not having to support things still running on Python
2, I would move to Python 3.3 and not look back.  Except, yes, there are
still libraries that haven't made the change....blast!

Python 2.7 is there if your software was written to run on the 2 series.  I
am sure it will either be distributed with (as default or option) major
operating systems for some time.  I am totally unpersuaded by the argument
that 'back porting' more and more into Python 2 will ease the transition.
 I think it will just use up developer time, and delay further the day when
releasing new code for Python 3 only becomes not only reasonable but the
natural and default choice.

I am really glad to see that at least one distribution of Linux is moving
to Python 3 as the default.  I'd much rather see developer time spent
improving Python 3 than managing a transition.

I realised when Python 3.0 came out that eventually I would have to move to
Python 3.  I spent the next release in a state of denial.  But I had years
to get used to it, and I'm glad I have.  It "feels" more robust.  Of
course, I haven't ported every little program: but no one is forcing me
too!

All of these threads are written as if everyone's code is about to be
broken.  It isn't.  But if you want the new features, you need to make a
move, and it is probably time to write all new code in Python 3. If there's
a dependency holding you back, then there will be a Python 2 interpreter
around to run your code.  That all seems pretty reasonable and
straightforward to me.

Nicholas

--001a1132f112c28f7304ef54f5b6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I hardly know which of the various threads on this topic to reply to!<div><=
br></div><div>No one is taking Python 2.7 away from anyone. =A0It is going =
to be on the net for years to come. =A0Goodness! I expect if I wanted to go=
 and download Python 1.5 I could find it easily enough.</div>
<div><br></div><div>Like everyone else, when Python 3 came out I was nervou=
s. =A0A lot of my code broke - but it broke for a good reason. =A0I had bee=
n being cavalier about strings and ASCII and bytes. =A0A lot of my code was=
 working by accident rather than by design, or because my users had never f=
ed it anything that would make it fall over. =A0Of course, my first reactio=
n was a defensive one, but once I had got over that and got my head around =
Python 3&#39;s view of the world, I was pleased I had. =A0I find writing in=
 Python 3 leads to more robust code. =A0I like the way it forces me to do t=
he right thing, and I like the way it raises errors if I try to get away wi=
th something I shouldn&#39;t. Going back to Python 2 now feels a bit like s=
tepping back to the seductive and permissive hell of PHP in some ways!=A0 I=
f I could be sure that I was coding just for me and not having to support t=
hings still running on Python 2, I would move to Python 3.3 and not look ba=
ck. =A0Except, yes, there are still libraries that haven&#39;t made the cha=
nge....blast!</div>
<div><br></div>Python 2.7 is there if your software was written to run on t=
he 2 series. =A0I am sure it will either be distributed with (as default or=
 option) major operating systems for some time. =A0I am totally unpersuaded=
 by the argument that &#39;back porting&#39; more and more into Python 2 wi=
ll ease the transition. =A0I think it will just use up developer time, and =
delay further the day when releasing new code for Python 3 only becomes not=
 only reasonable but the natural and default choice.<div>
<br></div><div>I am really glad to see that at least one distribution of Li=
nux is moving to Python 3 as the default. =A0I&#39;d much rather see develo=
per time spent improving Python 3 than managing a transition.</div><div>=A0=
=A0<div>
I realised when Python 3.0 came out that eventually I would have to move to=
 Python 3. =A0I spent the next release in a state of denial. =A0But I had y=
ears to get used to it, and I&#39;m glad I have. =A0It &quot;feels&quot; mo=
re robust. =A0Of course, I haven&#39;t ported every little program: but no =
one is forcing me too! =A0</div>
<div><br></div><div>All of these threads are written as if everyone&#39;s c=
ode is about to be broken. =A0It isn&#39;t. =A0But if you want the new feat=
ures, you need to make a move, and it is probably time to write all new cod=
e in Python 3. If there&#39;s a dependency holding you back, then there wil=
l be a Python 2 interpreter around to run your code. =A0That all seems pret=
ty reasonable and straightforward to me.</div>
<div><br></div>Nicholas</div>

--001a1132f112c28f7304ef54f5b6--