From owner-freebsd-python@freebsd.org Mon Jan 30 04:27:47 2017 Return-Path: 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 DA400CC7166 for ; Mon, 30 Jan 2017 04:27:47 +0000 (UTC) (envelope-from lifanov@FreeBSD.org) Received: from mail.lifanov.com (mail.lifanov.com [206.125.175.12]) (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 AACAC1150 for ; Mon, 30 Jan 2017 04:27:47 +0000 (UTC) (envelope-from lifanov@FreeBSD.org) Received: from [192.168.1.102] (unknown [107.15.73.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.lifanov.com (Postfix) with ESMTPSA id 74C4E239433 for ; Sun, 29 Jan 2017 23:18:17 -0500 (EST) Subject: Re: Proposal: default to concurrent To: freebsd-python@freebsd.org References: From: Nikolai Lifanov Message-ID: <170c35c9-eb37-92b7-3224-54f451f1e21c@FreeBSD.org> Date: Sun, 29 Jan 2017 23:18:11 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="DNWIBClh0mU24Cvhhr2unpO00dtEPVbws" X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2017 04:27:48 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --DNWIBClh0mU24Cvhhr2unpO00dtEPVbws Content-Type: multipart/mixed; boundary="mcd4NCjmhD7HuKmBbpNX7oEJtsex8Vsv5"; protected-headers="v1" From: Nikolai Lifanov To: freebsd-python@freebsd.org Message-ID: <170c35c9-eb37-92b7-3224-54f451f1e21c@FreeBSD.org> Subject: Re: Proposal: default to concurrent References: In-Reply-To: --mcd4NCjmhD7HuKmBbpNX7oEJtsex8Vsv5 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 01/29/17 14:08, John W. O'Brien wrote: > Hello FreeBSD Python, >=20 > One of the most common problems I encounter with python3 > interoperability is when the concurrent option is needed and can be > trivially enabled. There is a growing list of bugs where this, on a > individual port basis, has been fixed ([0], [1]), is in progress ([2], > [3]), or is in my queue and perhaps others' to submit ([4]). On the > other hand, there are lots of ports for which concurrent is a no-op, an= d > lots more that don't support python3 at all meaning that concurrent has= > little to no chance to cause harm. >=20 > What I propose is to enable the concurrent behavior by default and to > provide a feature to disable it when necessary. >=20 > I welcome supportive and dissenting comments as well as cautionary > remarks about the likely pitfalls of pursuing this. >=20 > > While it would be tempting to call the new feature something > unflattering like "i_hate_python3" or "archaic_upstream" or > "regressive", the most natural name is probably just "noconcurrent". > >=20 > Regards, > John >=20 > [0] textproc/py-xlrd: Allow concurrent installs > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209689 > [1] [PATCH] textproc/py-xlsxwriter: Enable concurrent installs > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215331 > [2] textproc/py-pygments: add concurrent to USE_PYTHON > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214295 > [3] math/py-bottleneck: bump to 1.20, install concurrently > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215263 > [4] devel/py-boto, devel/py-tables, devel/pep8, devel/flake8 >=20 I think the biggest controversy is that binary names are suffixed, which may not be what upstream projects like and/or document. It may be confusing to users as well. If we can get rid of the suffix for PYTHON_CONCURRENT_INSTALL for whichever version is PYTHON_DEFAULT, it should be a net positive to treat it the same way we did USE_GCC in the past (enable PYTHON_NO_CONCURRENT or something and remove it on per-port basis once fixed). - Nikolai Lifanov --mcd4NCjmhD7HuKmBbpNX7oEJtsex8Vsv5-- --DNWIBClh0mU24Cvhhr2unpO00dtEPVbws Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKoBAEBCgCSFiEE5oT6TcuaWvG5gtjzZ6sv56ecR0UFAliOvohfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU2 ODRGQTREQ0I5QTVBRjFCOTgyRDhGMzY3QUIyRkU3QTc5QzQ3NDUUHGxpZmFub3ZA ZnJlZWJzZC5vcmcACgkQZ6sv56ecR0WJTQ/9He1FKY6tNzGM8nZn0pr/9SUtsykm eg6Z/OwxgSgV9p5Tkp4kFlPPLzkconVqESJGy9slhLqFjL1CiG8CfzfY0T2S8IrS wC9WEzqxTJ4Zo/DYjynH3+usFLBcCANdA5kpsdUW4RAgRk4D6qLuLfAeAuhvNLkO e5s6oVSwKIZ5Pq0OuTnC3Fqf0dXv7zrxPLh1E8fKEHEKj25LYA15tCUFTLghFTg8 wUWjKa6fQ+Tzjs1nFk4vOfsmVyQigwqCOQbfEyqcEEPS5UHrfwBTjJows+DpqtSX pzFSnSqYvYgWep6/yP1s2mEAjEvwD3Bj3q522fOF4FoQlx2l7Ai6+oA0vvqwzHXJ lL2jmTn96jwXeQ8hP/L7DoqRcjJNykJjz5HebzrCijvW+7DjRyQvTV6in+4SPYgZ jr/lUuRgdYL6cyf/JZliWixVL71Aq2gFE6PBNzF+JZkLcsfQY02PM8nSEm0S52j+ iCoxFlSstUPmqCy4ksgexHxXfyStG5TbBHqamVD2vuZwFOtT5r2xi3RkuWgKzaus f8vcNaQnVnko2+mXN8nsaXHSGs2W5m5YUwlvNeJM6PDkdRNjBDM1WUCffIeAkbiE qo+IjtwnFxb24vyb01L0HWG1Miq4vEy14IMlbzAZNr/CtnZqDnnTQtgoCC3NMaVi z7Xf+Z2q/l6mlLU= =5BwE -----END PGP SIGNATURE----- --DNWIBClh0mU24Cvhhr2unpO00dtEPVbws--