PythonMigrationStatus

Not logged in - Log In / Register

Revision 102 as of 2009-10-31 11:41:20

Clear message

Moving to newer Python versions

The ultimate goal is to migrate Launchpad to Python 2.6. Rather than go straight to Python 2.6, we are focusing on Python 2.5 first as a stepping stone. People involved in this effort: maxb, gary, salgado, barry, simono. We are treating this work as a sprint; come join us on #launchpad-sprint on freenode.

Update 2009-10-24: The sprint has concluded. We were successful in getting Launchpad to work under 2.5 + Zope Toolkit. Python 2.6 support will be postponed until the Lucid timeframe.

Relevant tagged bugs: https://bugs.launchpad.net/launchpad-foundations/+bugs?field.tag=python-upgrade

Branches

Review process

You should submit merge proposals into the appropriate branch. gary, salgado, and barry will review all branches and we'll use a lightweight review process to manage this (simple cover letters, 5-minute reviews). Once approved, you can land your change by just merging it into a pristine local copy of the destination and pushing it; there is no pqm gateway.

Merge flow

In general, we'll merge from devel -> ztk-2.5 -> python-migration2.6.

Things you'll need to do

Known/Open issues

Bustimications

Cleanup potential


Python 2.5 w/Zope Toolkit

This is a branch off of python-migration which uses Python 2.5 and the Zope Toolkit.

test failures


Python 2.6

This is the ztk-2.5 branch, converted to use Python 2.6.

Also, a multitude of modules of modules (sha, md5, sets, ...) are deprecated in Python 2.6, and many tests will fail merely because of unexpected DeprecationWarnings (but see below).

Getting started

Test failures