Date: Mon, 02 May 2016 16:15:34 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 209204] Changing default Python version unduly difficult Message-ID: <bug-209204-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209204 Bug ID: 209204 Summary: Changing default Python version unduly difficult Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Ports Framework Assignee: portmgr@FreeBSD.org Reporter: mi@FreeBSD.org CC: freebsd-ports-bugs@FreeBSD.org, kde@FreeBSD.org, python@FreeBSD.org Although I still have python-2.7 installed and used by some of the ports, I= 'd like the newly-built ones to be based on python-3.5. To this end I set the following flags: DEFAULT_VERSIONS=3Druby=3D2.0 tcl=3D8.6 gcc=3D4.9 db=3D6.1 python=3D3.5 per= l=3D5.22 ghostscript9:agpl PYTHON3_DEFAULT=3D3.5 PYTHON_DEFAULT=3D3 (even though only the very first one should be needed, right?) Despite all this, devel/py-sip, for example, still insists on using 2.7: PKGNAME=3Dpy27-sip-4.17,1 PYTHON_VER=3D2.7 The only way to force it, apparently, is to edit each port's Makefile and change USES=3Dpython to USES=3Dpython:3=20 This should not be necessary, should it? --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209204-21822>