how to enforce one version of python

Ruslan Makhmatkhanov cvs-src at yandex.ru
Tue Sep 11 14:58:02 UTC 2018


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


More information about the freebsd-ports mailing list