Supporting Python 3 (Support Python3)--about the book

About the book

This book is the source code in the github[5] open book, so anyone can contribute to this book (in the Lake, the original version of the text to provide a PDF, the purchase price can be self-determined, conditional advice to support). Authors and editors are Lennart Regebro, and later contributors will be listed here.

This book is in Restructuredtext[1], written in, using sphinx[2] and latex[3] typesetting and using createspace[4]. Printing. Fonts for each part: TeX Gyre schola body text, Dejavu Sans Mono code, and flux Bold title.

Cover from Emmanuel "Tambako" Keller, http://www.flickr.com/photos/tambako/

On the page of this book there is a errata, http://python3porting.com/.

Lennart Regebro (in the lake to smell the camphor: the author) would like to thank the following for those who provide help:

Andreas Braukmann, Nicholas Coghlan, Paul Everitt, Cris Ewing, Luca Fabbri , Russell ferriday, Patrick gerken, Janko Hauser, domen ko?ar, Baptiste Mispelon , Alexander Pilz,Johannes raggam, Luciano Ramalho, Matt Russell, Christian theune, Sébastien verbois and Ian Watt donated generously to make the book a community effort.

Brett Cannon wrote the preface.

Martin von L?wis has reviewed the book with his technology and provided essential feedback, as well as distribute and Zope.interface, who have provided a lot of help in supporting Python3 early.

godefroid Chapelle, Jasper spaans and Wyn Williams Review the contents, grammar and errors of the book.

Brandon Craig Rhodes wrote the first chapter when the book was an idea on Python magazine.

A Note on terminology

The process of switching to Python 3 are most often called "porting". The first and editions of the book is also called "Porting to Python 3". However, this gave the false impression the is a lot of work, and that Python 3 was "a different language" than Pyt Hon 2. Although moving to Python 3 can being hard work, for the most time it's isn't, and as Python 2.5 and Python 3.2 is rapidly FA Lling out of use, it gets even easier.

For that reason, I changed the name of the "supporting Python 3" as this better reflects the effort. It ' s not porting, the vast majority of your code would work with no changes, or changes that can is done automatically with 2to3.

I have tried to avoid using the word "porting" in the text as a part of this.

Footnotes

[1]	Http://docutils.sourceforge.net/rst.html

[2]	http://sphinx.pocoo.org/

[3]	http://www.latex-project.org/

[4]	https://www.createspace.com/

[5]	Https://github.com/regebro/supporting-python-3

In the lake to hear the original: in the http://python3porting.com/about.html

Supporting Python 3 (Support Python3)--about the book