launchpad-dev team mailing list archive

[James Westby <jw+debian@xxxxxxxxxxxxxxx>]

On Thu, 4 Mar 2010 18:45:26 -0300, Sidnei da Silva <sidnei.da.silva@xxxxxxxxx> wrote:
> On Thu, Feb 4, 2010 at 4:40 PM, Jamu Kakar <jkakar@xxxxxxxx> wrote:
> > Hi,
> >
> > On Tue, Feb 2, 2010 at 10:12 AM, Barry Warsaw <barry@xxxxxxxxxxxxx> wrote:
> >> James checked with Jamu about Landscape.  They're still on 2.5 but he
> >> apparently does not think getting to 2.6 is going to be difficult for them.
> >> I'm not sure about U1.
> >
> > Our client runs on python2.6 now.  I believe the only package we
> > have on the server side that will need attention before we move to
> > python2.6 is Zope 3 (specifically, lp:~landscape/zope3/trunk).
> > We're currently running it on python2.5.  Ideally, instead of fixing
> > our branch, we'd move to a shared Zope package (or a collection of
> > eggs, or ...).
> >
> > I haven't actually tried to make the branch work with python2.6, and
> > maybe it's harder than I think it will be.  So yeah, I'm
> > optimistic. :)
> 
> FWIW, Landscape trunk now works with *both* Python 2.5 and 2.6, with
> just a make variable switch. Our plan is now to get our Staging
> servers moved to Python 2.6 ASAP. Speaking of which, where is this
> magical PPA containing backports of Python 2.6 to Hardy?

https://edge.launchpad.net/~python-dev/+archive/ppa I think, Matthias
can confirm.

That may not be all you need depending on whether you use any packages
with binary extensions, and how the packaging helper tools behave given
the new release, but it's a base to build on.

Thanks,

James