From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 14:26:13 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 322F81065674; Tue, 30 Aug 2011 14:26:13 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward11.mail.yandex.net (forward11.mail.yandex.net [IPv6:2a02:6b8:0:801::1]) by mx1.freebsd.org (Postfix) with ESMTP id 497088FC0C; Tue, 30 Aug 2011 14:26:12 +0000 (UTC) Received: from smtp13.mail.yandex.net (smtp13.mail.yandex.net [95.108.130.68]) by forward11.mail.yandex.net (Yandex) with ESMTP id E49DFE829BA; Tue, 30 Aug 2011 18:26:10 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314714370; bh=nJr1MNayoE61hgTZ593mWr9zcbOC/38rNlMXQ7OVtuc=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=kLoSt3RWyB3aEqhCP1+WeYiZuZlxvjmVRB9esxlvJWIePYHRSktzYSF9qz4zGiku5 WaIFnqJB9nmkOka/n3Pv7GTB8BXCyEIGW/q3yl+Pt7KZ1IlWlgRcqlTwNQpI9A2k7z qlDF0/a2o9XxTdpCQZK0GP+wTjt5iBo7Tw6WZUzg= Received: from smtp13.mail.yandex.net (localhost [127.0.0.1]) by smtp13.mail.yandex.net (Yandex) with ESMTP id C4BF4E402B6; Tue, 30 Aug 2011 18:26:10 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp13.mail.yandex.net (nwsmtp/Yandex) with ESMTP id QAmSaNin; Tue, 30 Aug 2011 18:26:10 +0400 X-Yandex-Spam: 1 Message-ID: <4E5CF2FF.5080302@yandex.ru> Date: Tue, 30 Aug 2011 18:26:07 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: glarkin@FreeBSD.org References: <4E5CE015.70803@FreeBSD.org> <4E5CE7BB.8050808@yandex.ru> <4E5CEC1E.5010209@FreeBSD.org> In-Reply-To: <4E5CEC1E.5010209@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports Mailing List , miwi@FreeBSD.org Subject: Re: Python min version bumped from 2.4+ to 2.5+ X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 14:26:13 -0000 Greg Larkin wrote on 30.08.2011 17:56: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 8/30/11 9:38 AM, Ruslan Mahmatkhanov wrote: >> Greg Larkin wrote on 30.08.2011 17:05: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Hi Martin, >>> >>> I have a question about a commit you made in February 2011: >>> http://www.freshports.org/commit.php?message_id=201102250750.p1P7ofDg016541@repoman.freebsd.org&files=yes >>> >>> >>> Part of the commit changed: >>> >>> USE_PYTHON= 2.4+ >>> >>> to >>> >>> USE_PYTHON= 2.5+ >>> >>> Was there a specific reason for doing so? I am running various >>> tinderbox builds to check on port usage of the USE_PYTHON variable, and >>> I noticed that devel/py-setuptools no longer builds if Python 2.4 is >>> selected. >>> >>> I'd like to restore that capability, but before I send a PR, I wanted to >>> check with you first. >>> >>> Thank you, >>> Greg >>> - -- >>> Greg Larkin >>> >>> http://www.FreeBSD.org/ - The Power To Serve >>> http://www.sourcehosting.net/ - Ready. Set. Code. >>> http://twitter.com/cpucycle/ - Follow you, follow me >> >> I'm sorry for sail in, but i think that the reason is that python24 is >> reached it's EOL long time ago. Actually the only supported python >> releases atm according to python.org are - 2.7.2 and 3.2.1, and >> developers highly encourages the users to move to this versions. >> >> 2.5 and 2.6 are in security-fix-only mode, there will be no ANY releases >> for this branches after October 2011 and October 2013 respectively, >> while 2.4 does not get security-fixes even. >> >> There is also this answer from Martin in this pr: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/155526: >> >> python24 goes to the end of month, this port is on the todo for removal >> > > Hi Ruslan, Hi Greg > > Ok, thank you for the explanation. Shall I mark python24 for removal > from the tree or file a PR for python@ to do it? It's not so easy actually, since we have many ports in the tree that still depend on 2.4 (notably all that zope/plone stuff) and i believe it was the reason why python24 still not be removed in the first place. I do some work about eliminating python24 usage in the tree (yesterdays py-pysqlite2x stuff - one of it), but it's not that fast. I also working on porting zope2.13/plone4 (that supports python 2.6 and 2.7) and i'm planing to finish it this weekend after proper testing. After that we can deprecate/remove existing zope/plone (not longer supported upstream). > > FYI, I have been running tinderbox builds with PYTHON_VERSION and > PYTHON_DEFAULT_VERSION set to python2.4, python2.5, etc. to find out if > ports with USE_PYTHON=yes need to be constrained a bit more. Yes, there is a lot of work. We have USE_PYTHON with bogus values like 1.5+, 1.6+, 2.0+ etc :). And most of python ports will not work with python3x so they should be constrained with -2.7 too. > I figured that python2.4 was supported since it was still in the tree > and wasn't marked for removal yet, but I admin that I didn't check > python.org for confirmation. As i already stated, i believe it's still there because there is dependent ports. And as far i know in linux world noone shipping python24 this days. Even RHEL/CentOS finally switched to 2.6.5 in their 6.x branches. > > Regards, > Greg > - -- > Greg Larkin > > http://www.FreeBSD.org/ - The Power To Serve > http://www.sourcehosting.net/ - Ready. Set. Code. > http://twitter.com/cpucycle/ - Follow you, follow me -- Regards, Ruslan Tinderboxing kills... the drives.