Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Jan 2017 15:40:15 -0500
From:      "John W. O'Brien" <john@saltant.com>
To:        Eitan Adler <lists@eitanadler.com>
Cc:        FreeBSD Python List <freebsd-python@freebsd.org>, Marcus von Appen <mva@freebsd.org>
Subject:   Re: Proposal: default to concurrent
Message-ID:  <14c681de-917b-4737-13a8-dc7b9256969a@saltant.com>
In-Reply-To: <CAF6rxg=96giSsOS5MQBEujbFNKzCHk%2BF2sanjH7sOJ4nE_5Y=A@mail.gmail.com>
References:  <b331f7bb-f258-e157-45bb-20cec74b54f0@saltant.com> <CAF6rxg=96giSsOS5MQBEujbFNKzCHk%2BF2sanjH7sOJ4nE_5Y=A@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--fXemLqX1FuOgx9XERFIv8MgmFodOtNA3c
Content-Type: multipart/mixed; boundary="BR7ecFOjL4aQRVudWg39ebh8dML7Q8x3H";
 protected-headers="v1"
From: "John W. O'Brien" <john@saltant.com>
To: Eitan Adler <lists@eitanadler.com>
Cc: FreeBSD Python List <freebsd-python@freebsd.org>,
 Marcus von Appen <mva@freebsd.org>
Message-ID: <14c681de-917b-4737-13a8-dc7b9256969a@saltant.com>
Subject: Re: Proposal: default to concurrent
References: <b331f7bb-f258-e157-45bb-20cec74b54f0@saltant.com>
 <CAF6rxg=96giSsOS5MQBEujbFNKzCHk+F2sanjH7sOJ4nE_5Y=A@mail.gmail.com>
In-Reply-To: <CAF6rxg=96giSsOS5MQBEujbFNKzCHk+F2sanjH7sOJ4nE_5Y=A@mail.gmail.com>

--BR7ecFOjL4aQRVudWg39ebh8dML7Q8x3H
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 1/29/17 14:22, Eitan Adler wrote:
> On 29 January 2017 at 11:08, John W. O'Brien <john@saltant.com> wrote:
>> Hello FreeBSD Python,
>> On the
>> other hand, there are lots of ports for which concurrent is a no-op, a=
nd
>> lots more that don't support python3 at all meaning that concurrent ha=
s
>> little to no chance to cause harm.
>>
>> What I propose is to enable the concurrent behavior by default and to
>> provide a feature to disable it when necessary.
>=20
>=20
> 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


--BR7ecFOjL4aQRVudWg39ebh8dML7Q8x3H--

--fXemLqX1FuOgx9XERFIv8MgmFodOtNA3c
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYjlMwAAoJEGEAJpqmdExHQVQP/3Gv1Y7zWCDopy3cCV7hXYV3
SOCxilfD8CNdt1/2YWD0vijGaoP8MLMwXEZq5jHKq8tbADef3NRpv+GloyebPNrC
WRzP8ydoFzi9hVJRZosnz3iOZPpRm32yU6GN8OG5rasVcueYE2slU8Y0lKbXCdTV
n5qYrjhZkxede7KobB3mtk6Qx6TbF5jqXm+PTddCLje7+xes213uAUowfQYbECYu
BOCzKT0te3nwivt8sk2wbfYjsyvveKWJpjPH5pLdFROiRUxtSkfgCTYxokTYhJ4n
ddJCpX2JDIxgxlNcoDIGeJI29P7At15dWnOtpaYTK5ruSxDJR8cI0gAuHmELdYhD
DwcO5q2ZGvxwX70e1yfIOJXX3GO0yycR4/Mk+i6qeg3t8wrM0hG7S0nkG9VtjxE9
tvxM1Q3x4WyxCL+4T0VnXdJ8MrTMZpEerH6sbB+eAMWnhQe5VLikeNjFXiuh44qK
ycXN2AmNNdnQrXxdkSa5B4fTp4K9/qTzbs+af+xXgLbJ0WtBmNiZ62tzLPXPyp++
HoGcoeFnzC2tEKr/6eRzUQ7MnS2xWF67ZPm1sSypteWSGwtzcQUAcz7PLgDlz4aR
txxhaH87LH9GO3bO+FVQYITDfUAL545HkA7sVDzTXzf/ivXa9i7wVwZjH5owR8IF
TujZRyBI5QI34cvrq+xg
=NOlY
-----END PGP SIGNATURE-----

--fXemLqX1FuOgx9XERFIv8MgmFodOtNA3c--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14c681de-917b-4737-13a8-dc7b9256969a>