From owner-freebsd-python@freebsd.org  Mon Jan 30 06:44:21 2017
Return-Path: <owner-freebsd-python@freebsd.org>
Delivered-To: freebsd-python@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9772BCC704F
 for <freebsd-python@mailman.ysv.freebsd.org>;
 Mon, 30 Jan 2017 06:44:21 +0000 (UTC) (envelope-from mva@FreeBSD.org)
Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de
 [80.67.31.41])
 (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 5E0F8BE6
 for <freebsd-python@freebsd.org>; Mon, 30 Jan 2017 06:44:20 +0000 (UTC)
 (envelope-from mva@FreeBSD.org)
Received: from [77.188.73.156] (helo=[192.168.35.21])
 by smtprelay03.ispgateway.de with esmtpsa
 (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84)
 (envelope-from <mva@FreeBSD.org>)
 id 1cY5h5-0000O2-Ir; Mon, 30 Jan 2017 07:44:03 +0100
From: "Marcus von Appen" <mva@FreeBSD.org>
To: "John W. O'Brien" <john@saltant.com>, "Eitan Adler" <lists@eitanadler.com>
Subject: Re[2]: Proposal: default to concurrent
Cc: "FreeBSD Python List" <freebsd-python@freebsd.org>
Date: Mon, 30 Jan 2017 06:44:11 +0000
Message-Id: <em86ff578b-18b7-4981-a88f-59a7bab846fd@hora>
In-Reply-To: <14c681de-917b-4737-13a8-dc7b9256969a@saltant.com>
References: <b331f7bb-f258-e157-45bb-20cec74b54f0@saltant.com>
 <CAF6rxg=96giSsOS5MQBEujbFNKzCHk+F2sanjH7sOJ4nE_5Y=A@mail.gmail.com>
 <14c681de-917b-4737-13a8-dc7b9256969a@saltant.com>
Reply-To: "Marcus von Appen" <mva@FreeBSD.org>
User-Agent: eM_Client/7.0.27943.0
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Df-Sender: ZnJlZWJzZEBzeXNmYXVsdC5vcmc=
X-BeenThere: freebsd-python@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-python>, 
 <mailto:freebsd-python-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python/>
List-Post: <mailto:freebsd-python@freebsd.org>
List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-python>,
 <mailto:freebsd-python-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jan 2017 06:44:21 -0000

On 1/29/2017 9:40:15 PM, "John W. O'Brien" <john@saltant.com> wrote:

>On 1/29/17 14:22, Eitan Adler wrote:
>>  On 29 January 2017 at 11:08, John W. O'Brien <john@saltant.com>=20
>>wrote:
>>>  Hello FreeBSD Python,
>>>  On the
>>>  other hand, there are lots of ports for which concurrent is a no-op,=
=20
>>>and
>>>  lots more that don't support python3 at all meaning that concurrent=
=20
>>>has
>>>  little to no chance to cause harm.
>>>
>>>  What I propose is to enable the concurrent behavior by default and=20
>>>to
>>>  provide a feature to disable it when necessary.
>>
>>
>>  silly question but why is it an option in the first place?
>
>Not at all silly. I can only guess at the answer though. Let's consult
>its implementer [0].
>
>[0] https://svnweb.freebsd.org/ports?view=3Drevision&revision=3D356921
>
Because at that time python ports existed, which did not build cleanly=20
with python3,
but which were dependencies to many other ports. The situation may have=20
changed
now.

Cheers
Marcus