From owner-freebsd-python@freebsd.org Tue May 21 01:05:46 2019 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE58A159900F for ; Tue, 21 May 2019 01:05:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5C3936CA11 for ; Tue, 21 May 2019 01:05:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 194AE159900B; Tue, 21 May 2019 01:05:46 +0000 (UTC) Delivered-To: python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E5DA7159900A for ; Tue, 21 May 2019 01:05:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 779946CA0C for ; Tue, 21 May 2019 01:05:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id BE93A9462 for ; Tue, 21 May 2019 01:05:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x4L15isp088189 for ; Tue, 21 May 2019 01:05:44 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4L15iEt088188 for python@FreeBSD.org; Tue, 21 May 2019 01:05:44 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 237952] mail/notmuch: port still has build dependency python27 Date: Tue, 21 May 2019 01:05:44 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc see_also Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 May 2019 01:05:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237952 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |timur@FreeBSD.org See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 237 | |61 --- Comment #4 from Kubilay Kocak --- The talloc port is currently set to limit Python support to 2.7, which was added in ports r454556 ("Fix too broad Python specification, cut down to 2.7 explicitly.) where it previously declared 2.7+, but why is was too broad is= not detailed. Looking for previous issues in Bugzilla, it appears bug 223761 was the originator of limiting it to 2.x. Building talloc after removing only the 2.7 restriction, results in a build error as follows: =3D=3D=3D> Configuring for talloc-2.1.14 Traceback (most recent call last): File "buildtools/bin/waf", line 75, in import Scripting File "/wrkdirs/usr/ports/devel/talloc/work/talloc-2.1.14/third_party/waf/wafadmi= n/Scripting.py", line 146 except Utils.WafError, e: ^ SyntaxError: invalid syntax See Also: https://trac.macports.org/ticket/30617 (and my other google resul= ts) The port also uses USES=3Dwaf (but does *not* specify WAF_CMD), which conta= ins the following: .if !${USES:Mpython*} python_ARGS=3D 2.7,build .include "${USESDIR}/python.mk" .endif Upstream says Python 2 and 3 are supported [1], so I don't know why this is limited to 2.7 either. The bundled waf script (WRKSRC/buildtools/bin) is "./waf --version waf 1.5.= 19 (9709M)" waf moved to Python 3 syntax by defaultin: NEW IN WAF 1.6.0 ---------------- General: * Python 3 syntax by default (runs unmodified for 2.6, 2.7, 3.0 and 3.1) There is an additional section after USES is set in the port: # XXX: This is a gross hack to make port use both Python 2.7+ and 3.3+ # This is not officially supported, use at your own risk .if defined(WITH_SAMBA4_PYTHON3) && ${WITH_SAMBA4_PYTHON3:M3\.[0-9]} which allows the user to specify those variables and add 'additional' python version support via ./configure: --extra-python=3DPYTHON build selected libraries for the specified additional version of Python (example: --extra-python=3D/usr/bin/python3) [1] https://gitlab.com/ita1024/waf/ "Python compatibility: cPython 2.5 to = 3.x, Jython 2.5, IronPython, and Pypy" --=20 You are receiving this mail because: You are on the CC list for the bug.=