Date: Mon, 1 Feb 2021 04:02:16 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: Don Lewis <truckman@freebsd.org> Cc: Antoine Brodin <antoine@freebsd.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r563515 - in head: devel/py-pymtbl net/py-pynmsg Message-ID: <20210201040216.GA45748@FreeBSD.org> In-Reply-To: <tkrat.4a34e6b0dacf2469@FreeBSD.org> References: <202101311905.10VJ5kFO025821@repo.freebsd.org> <tkrat.4a34e6b0dacf2469@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 31, 2021 at 07:36:14PM -0800, Don Lewis wrote: > On 31 Jan, Antoine Brodin wrote: > > New Revision: 563515 > > URL: https://svnweb.freebsd.org/changeset/ports/563515 > > > > Log: > > Remove python 2.7 support (insert usual complaint about insufficiently descritptive commit logs here) > ... > > -USES= pkgconfig python shebangfix uniquefiles:dirs > > +USES= pkgconfig python:3.6+ shebangfix uniquefiles:dirs > > USE_PYTHON= autoplist cython distutils > > Question, won't there be additional churn when we clean up after the > removal of python 2 (or 3.6 if that happens first)? > > If I do a build without specifying a flavor, the flavor for the default > python (3) version is built. > > FWIW, this code is compatible with both python 2 and python 3. As this question had been asked previous and I didn't see a reply, I guess that at this point new ports are not allowed to declare pre-3.6 support even if they actually do. This probably has something to do with 2.7 removal happening real soon now, however, how exactly does this help is unclear to me. :-) I also share the extra churn concerns. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210201040216.GA45748>