A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2018-May/153507.html below:

[Python-Dev] (Looking for) A Retrospective on the Move to Python 3

[Python-Dev] (Looking for) A Retrospective on the Move to Python 3 [Python-Dev] (Looking for) A Retrospective on the Move to Python 3Eric S. Raymond esr at thyrsus.com
Sat May 12 03:05:02 EDT 2018
Steven D'Aprano <steve at pearwood.info>:
> So not all Python 3 migration stories turn into horror stories :-)

Peter Donis and wrote "Practical Python porting for systems programmers":

http://www.catb.org/esr/faqs/practical-python-porting/

We developed and applied these techniques on src (a lightweight version-control
system for single-contributor projects), reposurgeon (a tool for surgery
on version-control repositories, 14KLOC), doclifter (man-page to XML-DocBook
markup lifter, 8KLOC), the Python components of GPSD (9KLOC) and the Python
components of NTPSec (secure network time service, 16KLOC).

All this code runs under either 2 nor 3 without requiring six or any other
shim library.  Applying the techniques is not particularly difficult. There
were no horror stories at any point.

I expect to keep writing Python in this polyglot idiom until 2 is obsolete
enough to fall off the radar.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4