Date: Wed, 18 May 2016 03:09:41 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 209551] Python bits ignore DEFAULT_VERSIONS Message-ID: <bug-209551-21822-y9WxnbQwVo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209551-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-209551-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209551 Iblis Lin <iblis@hs.ntnu.edu.tw> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iblis@hs.ntnu.edu.tw --- Comment #1 from Iblis Lin <iblis@hs.ntnu.edu.tw> --- Hi, I will propose that reordering priorities of those variables -- ${LOCALBASE}/bin/python and DEFAULT_VERSION. The state quo: if ${LOCALBASE}/bin/python exists: priority: PYTHON_VERSION > ${LOCALBASE}/bin/python > DEFAULT_VERSIONS else: priority: PYTHON_VERSION > DEFAULT_VERSIONS I think make `DEFAULT_VERSIONS` override `${LOCALBASE}/bin/python` will be better: priority: PYTHON_VERSION > DEFAULT_VERSIONS > ${LOCALBASE}/bin/python The PYTHON_VERSION still has the highest priority. This variable is handy for installing same ports with different python version at the same time. For example, I need the `database/py-sqlite3` installed for both py27 and py35. I just simply issue make with `PYTHON_VERSION`: make install clean PYTHON_VERSION=2.7 && make install clean PYTHON_VERSION=3.5 So, preserving the flexibility to override default is necessary; PYTHON_VERSION do it well currently. We just need to switch the order of 'local python' and DEFAULT_VERSION. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209551-21822-y9WxnbQwVo>