[Bug 209204] Changing default Python version unduly difficult
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon May 2 16:15:34 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209204
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 at FreeBSD.org
Reporter: mi at FreeBSD.org
CC: freebsd-ports-bugs at FreeBSD.org, kde at FreeBSD.org,
python at 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=ruby=2.0 tcl=8.6 gcc=4.9 db=6.1 python=3.5 perl=5.22
ghostscript9:agpl
PYTHON3_DEFAULT=3.5
PYTHON_DEFAULT=3
(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=py27-sip-4.17,1
PYTHON_VER=2.7
The only way to force it, apparently, is to edit each port's Makefile and
change USES=python to USES=python:3
This should not be necessary, should it?
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-python
mailing list