Date: Sun, 19 Jun 2016 07:50:51 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 209551] Python bits ignore DEFAULT_VERSIONS Message-ID: <bug-209551-21822-g6fyRsxJRN@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209551 --- Comment #5 from Kubilay Kocak <koobs@FreeBSD.org> --- @Mikhail, can you please provide a few example cases that show: - The port that is affected - The intended/expected result - The actual result - The result with any workarounds claimed to fix the issue (if there are an= y) Currently, and as far as I know/believe, the existing logic is intended as there are cases where the user-specified DEFAULT_VERSION of python desired,= may *not* be appropriate/correct for the port in question, based on the version= s of Python that port is declared to support (whether those declared are correct= or not). This is further complicated in dependency cases where some ports depe= nd on only one or more Python versions. A shorter way of saying the above is that the user literally cannot know, be expected to know, nor state the exact and only version of Python they want = to be used in any particular case. Obvious examples are:=20 - User specifies default version 3.x, port only supports 2.x - User specifies default version 2.x, port only supports 3.x - User specifies default version x.y, port explicitly does not work with x.y (say, for example, older 3.x versions) Having said that, there *are* ports in the tree right now that incorrectly, incompletely or inaccurately declare those versions. These all need to be fixed, with the documentation (at least in Uses/python) improved to make it clearer how to do it, and do it correctly. Examples are: Ports that specify USES=3Dpython:2 (or 3). This declaration means *only* th= at the port depends on the python2 or python3 *symlink* (and thus port). These sho= uld instead be USES=3Dpython:X.Y[+] or [-]X.Y, with an additional *_DEPENDS on = the respective lang/python{2,3} symlink port. Ports that specify X.Y+ arbitrarily, as almost all Python packages support = only up to the latest Python X.Y, and often break with future/newer ones until t= hey are tested/verified. Additionally, our USES syntax is unable to specify SOME version specificati= ons that are perfectly normal (and common) for Python packages. There is an open task documented here: https://wiki.freebsd.org/Python#Goals --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209551-21822-g6fyRsxJRN>