Chris Barker chris.barker at noaa.gov
Mon May 14 12:34:22 EDT 2018

• Previous message (by thread): [Python-Dev] (Looking for) A Retrospective on the Move to Python 3
• Next message (by thread): [Python-Dev] (Looking for) A Retrospective on the Move to Python 3
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Sat, May 12, 2018 at 8:14 AM, Skip Montanaro <skip.montanaro at gmail.com>
wrote:

> > I have found 2to3 conversion to be remarkably easy and painless.
>
> > And the whole Unicode thing is much easier.
>

Another point here:

between 3.0 and 3.6 (.5?) -- py3 grew a lot of minor features that made it
easier to write py2/py3 compatible code. u"string", b'bytes %i' % something
-- and when where the various __future__ imports made available?

If these had been in place in 3.0, the whole process would have been easier
:-(

-CHB

-- 

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20180514/edb8482f/attachment.html>

---

• Previous message (by thread): [Python-Dev] (Looking for) A Retrospective on the Move to Python 3
• Next message (by thread): [Python-Dev] (Looking for) A Retrospective on the Move to Python 3
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list