3

Differences between revisions 1 and 40 (spanning 39 versions)
Revision 1 as of 2012-04-19 16:50:35
Size: 1403
Editor: barry
Comment:
Revision 40 as of 2013-11-04 15:39:33
Size: 1461
Editor: barry
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
It is a release goal for Ubuntu 12.10 to have only Python 3 on the installation CD images. We have a [[https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-python-versions|Q-series]] blueprint for discussion of this goal at [[http://uds.ubuntu.com/|UDS-Q]] in Oakland, California, in May of 2012. There is a [[https://wiki.ubuntu.com/Python/FoundationsQPythonVersions|more detailed spec]] for this effort and a publicly shared [[http://tinyurl.com/7dsyywo|Google docs spreadsheet]] to track this effort. This is an ambitious effort that will only succeed with help from the greater Ubuntu, Debian, and Python communities. In other words, we need '''you'''! <<TableOfContents()>>
Line 5: Line 5:
At the bottom of this page, you will find various resources for diving more into aspects of supporting Python 3, from the pure-Python, C extension module, Debian packaging, and other perspectives. The intent of ''this'' page is to provide specific guidelines in a quick reference format, so that you only need to go here once you're familiar with the basic concepts and approaches, but need a refresher on specific coding techniques. This is a wiki page, and you are encouraged to contribute, but try to keep your recommendations tightly focused on accomplishing the release goal of Python 3 only on the 12.10 CDs. It is a release goal for Ubuntu 14.04 LTS to have only Python 3 on the desktop CD images. Also, we won't be allowing Python 2 on the Ubuntu touch images.
Line 7: Line 7:
== Resources == We've had blueprints for several Ubuntu releases, the latest of which is a [[https://blueprints.launchpad.net/ubuntu/+spec/core-1311-python3-roadmap|Trusty]] blueprint. There is a [[https://wiki.ubuntu.com/Python/FoundationsTPythonVersions|more detailed spec]] for this effort, an [[http://people.canonical.com/~ubuntu-archive/transitions/onlypy3oncd.html|official transition tracker]] and a publicly shared [[http://tinyurl.com/kgx7hsc|Google docs spreadsheet]] to track this effort. This is an ambitious effort that will only succeed with help from the greater Ubuntu, Debian, and Python communities. In other words, we need '''you'''!
Line 9: Line 9:
 * [[http://getpython3.com/|Python community portal to Python 3]] We'll track Ubuntu (and some Debian) related tasks here. This page used to contain a lot of good quick references for porting to Python 3, but that information has now moved [[http://wiki.python.org/moin/PortingToPy3k/BilingualQuickRef|to wiki.python.org]].


== Q/A ==

 * Why not rely on 2to3? 2to3 is a pretty slow tool so it can impede on the speed with which you develop your code. It can however be used in non-overwrite mode to get a good sense of what needs to be changed in your source code. Generally, a single-source approach is the best for bilingual (i.e. Py2 and Py3) Python apps.
 

Python 3 on Ubuntu

It is a release goal for Ubuntu 14.04 LTS to have only Python 3 on the desktop CD images. Also, we won't be allowing Python 2 on the Ubuntu touch images.

We've had blueprints for several Ubuntu releases, the latest of which is a Trusty blueprint. There is a more detailed spec for this effort, an official transition tracker and a publicly shared Google docs spreadsheet to track this effort. This is an ambitious effort that will only succeed with help from the greater Ubuntu, Debian, and Python communities. In other words, we need you!

We'll track Ubuntu (and some Debian) related tasks here. This page used to contain a lot of good quick references for porting to Python 3, but that information has now moved to wiki.python.org.

Q/A

  • Why not rely on 2to3? 2to3 is a pretty slow tool so it can impede on the speed with which you develop your code. It can however be used in non-overwrite mode to get a good sense of what needs to be changed in your source code. Generally, a single-source approach is the best for bilingual (i.e. Py2 and Py3) Python apps.

Python/3 (last edited 2016-02-26 01:40:43 by cmawebsite)