PythonMigrationStatus

Not logged in - Log In / Register

Revision 107 as of 2009-11-20 09:31:41

Clear message

Moving to newer Python versions

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

The ultimate goal is to migrate Launchpad to Python 2.6.

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

Branches

Review process

You should submit merge proposals into the 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

devel -> python-migration2.6.

Overview of content of the python-migration2.6 branch

I suspect we may decide to bin the python-migration2.6 branch, as much of its present content is either trivial shebang munging, or already cherrypicked into devel, or fixes which can be opportunistically landed on devel whilst it is still targetting 2.5. Therefore I'm making a checklist of the content of the branch:

Known/Open issues

Setup caveat

Bustimications

Cleanup potential

Situation

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