From owner-freebsd-python@FreeBSD.ORG Wed Jun 3 01:21:43 2015 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EAAF6D30; Wed, 3 Jun 2015 01:21:43 +0000 (UTC) (envelope-from venture37@geeklan.co.uk) Received: from host1.hosts.geeklan.co.uk (unknown [IPv6:2001:4978:254:48::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BEB1E1B19; Wed, 3 Jun 2015 01:21:43 +0000 (UTC) (envelope-from venture37@geeklan.co.uk) Received: from sevans-11-air.dhcp.lan.london.hackspace.org.uk (boole.london.hackspace.org.uk [82.69.229.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by host1.hosts.geeklan.co.uk (Postfix) with ESMTPSA id 7C0D77A3E3; Wed, 3 Jun 2015 02:21:41 +0100 (BST) Message-ID: <556E56A3.3060309@geeklan.co.uk> Date: Wed, 03 Jun 2015 02:21:39 +0100 From: Sevan Janiyan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Kubilay Kocak CC: Baptiste Daroussin , Dmitry Sivachenko , python@freebsd.org Subject: Re: Python's configure misunderstand freebsd References: <20150201233641.GH11558@ivaldir.etoilebsd.net> <6D628C1D-D289-4FB0-BC43-141B1828204B@gmail.com> <54CF84AB.9080306@FreeBSD.org> <556E53AB.6000003@geeklan.co.uk> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2015 01:21:44 -0000 On 03/06/2015 02:17, Kubilay Kocak wrote: > http://bugs.python.org/issue23817 > > Committed to the default branch. I tried to get it committed to the 2.7/3.4 > branches but there was an upstream lack of confidence on backward > compatibility. > > I can reopen the issue if need be. Apologies, I didn't realise this bug report had been raised and fixed. Looks like Victor needs some background: http://bugs.python.org/msg240381 but it's fine, as long as future versions will not require the patch, not a problem. It's your call :) Sevan