From owner-freebsd-ports@FreeBSD.ORG  Wed Jan 15 20:10:03 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 26905B8B
 for <freebsd-ports@freebsd.org>; Wed, 15 Jan 2014 20:10:03 +0000 (UTC)
Received: from chilled.skew.org (chilled.skew.org [70.90.116.205])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id F0779113A
 for <freebsd-ports@freebsd.org>; Wed, 15 Jan 2014 20:10:02 +0000 (UTC)
Received: from chilled.skew.org (localhost [127.0.0.1])
 by chilled.skew.org (8.14.7/8.14.7) with ESMTP id s0FJlOn5004036
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
 for <freebsd-ports@freebsd.org>; Wed, 15 Jan 2014 12:47:24 -0700 (MST)
 (envelope-from mike@chilled.skew.org)
Received: (from mike@localhost)
 by chilled.skew.org (8.14.7/8.14.7/Submit) id s0FJlOCG004035
 for freebsd-ports@freebsd.org; Wed, 15 Jan 2014 12:47:24 -0700 (MST)
 (envelope-from mike)
From: Mike Brown <mike@skew.org>
Message-Id: <201401151947.s0FJlOCG004035@chilled.skew.org>
Subject: USE_PYTHON version range no longer valid?
To: freebsd-ports@freebsd.org
Date: Wed, 15 Jan 2014 12:47:24 -0700 (MST)
X-Whoa: whoa.
X-Mailer: ELM [version 2.4ME+ PL126 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="UTF-8"
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 20:10:03 -0000

A port I maintain (sorta) can only be built under Python 2.2.1 through 2.4.x.
The app isn't being developed any longer, so patches to get it to build under
2.5+ aren't likely to be forthcoming.

The port Makefile previously had USE_PYTHON= 2.2-2.4, but it was changed this 
week to simply USE_PYTHON=2, with this comment:

  Python cleanup:
  - USE_PYTHON* = 2.X -> USE_PYTHON* = 2
  - USE_PYTHON* = 2.X+ -> USE_PYTHON* = yes
  Reviewed by:	python (mva, rm)
  Approved by:	portmgr-lurkers (mat)

By removing 2.4 as the maximum version, there are inevitable build errors for 
this app.

Reverting to USE_PYTHON= 2.2-2.4 results in 'make' failing with this:
===>  py27-4suite-1.0.b1_1 needs an unsupported version of Python.

I'm fine with that, although I'm unsure what the ramifications are of Python 
2.4 being unsupported. Do people have the option of installing Python 2.4.6 
and using it with this port, or do we need to decommission the port?