Date: Mon, 17 Oct 2016 14:03:28 +0200 From: "Vlad K." <vlad-fbsd@acheronmedia.com> To: freebsd-python@freebsd.org Subject: Re: Introducing python3 into user system Message-ID: <d4c8842780216a34f1395dac2e25cb82@acheronmedia.com> In-Reply-To: <a785c1ad-345e-8074-4f5a-3fc8af85f494@ze.tum.de> References: <c7c2d8eb-e512-b118-c432-25ca3ee094db@FreeBSD.org> <5893aa6d-5e29-81b5-9685-a04ab8260bcb@ze.tum.de> <60f3bedb-8f57-2703-7ee9-736fc26ff9d0@yandex.ru> <a785c1ad-345e-8074-4f5a-3fc8af85f494@ze.tum.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-10-17 13:27, Gerhard Schmidt wrote: > > 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. I agree with the bit of "let's not break systems", but not with the second part. Meanwhile, pkg variants will actually help going forward with ports that can run py35, enabling environments that want to be py35 exclusive while at the same time provide py27 environments where needed. So instead of "let's [do nothing and] discuss this in 4 years" I propose "let's see how to get variants going" :) https://reviews.freebsd.org/D5563 Because that 2.x EOL will come sooner than some would like and all those "let's discuss this later" systems will find themselves in hot water. I've been through that with PHP 5.3, needing to support clients that still, in 2016, required PHP <5.3 .... -- Vlad K.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d4c8842780216a34f1395dac2e25cb82>