Introducing python3 into user system

Gerhard Schmidt schmidt at ze.tum.de
Mon Oct 17 11:27:15 UTC 2016


Am 17.10.2016 um 12:39 schrieb Ruslan Makhmatkhanov:
> Gerhard Schmidt wrote on 10/17/2016 11:07:
>> Am 16.10.2016 um 21:22 schrieb Ruslan Makhmatkhanov:
>>> - if port has a build dependency upon python and it can be built both
>>> with python2 and python3, force it to build with python3
>>> - if some standalone application can be running both with python2 and
>>> python3 and it have equivalent python3 dependencies, force it to be run
>>> with python3
>>
>> What do you mean by "force it"?.
> 
> I mean set USES=python3.3+ for such ports.

This will install python3.5 on this system regardless if there is a
working python2.x installation, which is exactly what is wrong. I am a
software developer who runs legacy systems on python2.7. Forcing ports
that are able to run with python2.7 to install python3.5 will most
probably break my systems. USES should always represent the minimum
requirement not something so feel is something it should use.

Please do not break systems without a really good reason. This we can
discus in 4 years when support for python2 will end, but not until than.

Not everyone has the freedom to run only shine new software on shine new
systems.

Regards
  Estartu

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 847 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-python/attachments/20161017/84fbf9e5/attachment.sig>


More information about the freebsd-python mailing list