From owner-freebsd-python@FreeBSD.ORG Sun Jun 10 21:05:53 2007 Return-Path: X-Original-To: python@freebsd.org Delivered-To: freebsd-python@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3F78616A46E for ; Sun, 10 Jun 2007 21:05:53 +0000 (UTC) (envelope-from alexbl@FreeBSD.org) Received: from cherenkov.geekfire.com (cherenkov.geekfire.com [66.206.86.94]) by mx1.freebsd.org (Postfix) with ESMTP id 29B2213C465 for ; Sun, 10 Jun 2007 21:05:53 +0000 (UTC) (envelope-from alexbl@FreeBSD.org) Received: from localhost.my.domain (c-24-21-141-24.hsd1.or.comcast.net [24.21.141.24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by cherenkov.geekfire.com (Postfix) with ESMTP id DABA53B487; Sun, 10 Jun 2007 13:41:24 -0700 (PDT) From: Alexander Botero-Lowry To: "Hye-Shik Chang" , python@freebsd.org In-reply-to: <4f0b69dc0706101154r8a5b51btd81ffdc5a2321de3@mail.gmail.com> References: <4f0b69dc0706101154r8a5b51btd81ffdc5a2321de3@mail.gmail.com> Comments: In-reply-to "Hye-Shik Chang" message dated "Mon, 11 Jun 2007 03:54:23 +0900." Date: Sun, 10 Jun 2007 13:43:31 -0700 Sender: alex@localhost X-Peer: 127.0.0.1 Message-Id: <20070610204124.DABA53B487@cherenkov.geekfire.com> Cc: Subject: Re: Python 2.5.1 upgrade as a new default X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jun 2007 21:05:53 -0000 > Hello, > > I feel sorry about the slow progress of making 2.5 default. > I just updated the patch to the recent repository. > > http://people.freebsd.org/~perky/python25-rev5.diff > I've merged the revision 4 patch into a git repository at http://git.geekfire.com/?p=ports.git;a=shortlog;h=python25 It's on top of a fairly recent version of ports, with all conflicts resolved. > As some third-party packages started to use features of 2.5, > we'd better to move to 2.5 soon. Please review the patch > and scream if you have a problem with it. :) > Details for the patch are described in the previous mail [1]. > If no problem arises, I will commit it in the next week. > I'm concerned that we haven't fixed the problems that were found during pointyhat runs, portmgr@ wants this to be built on pointyhat before it goes into ports. I think we should be careful to make sure we've fixed the known build failures and then have pav@ do a pointyhat run for us.