Date: Tue, 11 Sep 2018 17:54:07 +0300 From: Ruslan Makhmatkhanov <cvs-src@yandex.ru> To: Baptiste Daroussin <bapt@FreeBSD.org>, tech-lists <tech-lists@zyxst.net> Cc: freebsd-ports@freebsd.org Subject: Re: how to enforce one version of python Message-ID: <4cd79546-c301-4ab7-13eb-3233736953f5@yandex.ru> In-Reply-To: <20180911145151.zgyeaiobnvkuo2rg@ivaldir.net> References: <fcb50bfe-c21f-a3ba-9d9f-2af92c3565d4@zyxst.net> <20180911145151.zgyeaiobnvkuo2rg@ivaldir.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Baptiste Daroussin wrote on 9/11/18 5:51 PM: > On Tue, Sep 11, 2018 at 03:28:15PM +0100, tech-lists wrote: >> Hi, >> >> There are a number of ports that seem to have their own preferential flavour >> of python, and some for example want to install python27 and python36 in the >> same place, and it's a pain when using portupgrade or similar tools. >> >> I have this in my /etc/make.conf: >> >> DEFAULT_VERSIONS+= python=2.7 >> >> Is this incorrect? I assume it must be, as for example devel/pylint >> (pylint-py27-1.9.2) wants to upgrade to pylint-py36-2.1.1 >> > That is because portupgrade is not flavor aware (or badly if it has been patched > to support flavors) > > Best regards, > Bapt No, it's because pylint2 as itself requires python > 3.4. User should switch to older devel/pylint1 if he needs to stick with 2.7. -- Regards, Ruslan T.O.S. Of Reality
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4cd79546-c301-4ab7-13eb-3233736953f5>