Date: Thu, 04 Nov 2021 05:00:24 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 259579] devel/py-circuitbreaker: Update to 1.3.2 Message-ID: <bug-259579-7788-NqvQG1H36g@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-259579-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-259579-7788@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=3D259579 --- Comment #6 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Alessandro Sagratini from comment #3) Python ports are declarative, not imperative, in that they declare what versions the package supports, rather than specifying or choosing a version. Whether any Python port language versions exists or doesn't exist in the tr= ee at any time, which changes over time, is not consequential. It is up to python.mk to determine the python version that will be used, ba= sed on:=20 1) the versions the port supports, and 2 what is available in the tree (on the user system), and 3) considering the version the user wants (DEFAULT_VERSIONS), and 4) what the current 'default version' version order is in python.mk tldr; specify the USES=3Dpython=3D<version-spec> as closely matching what u= pstream=20 upstream defines and/or tests against (sometimes they're not super precise = or up to date).=20 Note: there's certain things our version-spec format doesnt support, such as "!=3DX.Y" and multiple non-consecutive versions (like X.X,XZ) which are rar= ely needed. --=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-259579-7788-NqvQG1H36g>