On 25.8.2018 19:29, Andrew C Aitchison wrote:
On Tue, 21 Aug 2018, Miro Hrončok wrote:
> On 13.8.2018 11:49, Larry Hastings wrote on python-dev(a)python.org:
>> We of the core dev community commit to supporting Python releases for
>> five years. Releases get eighteen months of active bug fixes, followed
>> by three and a half years of security fixes. Python 3.4 turns 5 next
>> March--at which point we'll stop supporting it, and I'll retire as 3.4
>> release manager.
>>
>> My plan is to make one final release on or around its fifth birthday
>> containing the last round of security fixes. That's about seven
>> months from now.
>
> See also PEP 429 -- Python 3.4 Release Schedule [0].
>
> We have python34 and python36 in EPEL7. python34 being the "main" one
> and python36 the "other" one. The original plan [1] was that once the
> ecosystem is adapted well enough, we can switch what "main" and
> "other" is and eventually drop python34, creating room for maybe
> another python3 release to be the "other" next (python38 maybe?).
> Originally this was supposed to happen for each release [2], but this
> was later abandoned due to lack of manpower.
How does this affect EPEL6 ?
It doesn't. No python36 in EPEL 6. I guess it will just have an EOLed
Python 3.4 packaged until it's also EOLed.
We have just released singularity-runtime-2.6.0-1.1.el6.x86_64.rpm
which adds a dependency on /usr/bin/python3
Will EPEL6 users have to pull in an epel python3.6 as well as
epel python3.4 (and possibly in addition to SCL python33) ?
/usr/bin/python3 is provided by python34, so it will just use that.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok