On 28 July 2017 at 11:42, Miro Hrončok <mhroncok@redhat.com> wrote:
On 28.7.2017 16:25, John Dennis wrote:
I made this comment previously but because I think it's important I'm going to repeat it.

Yes, we hear you.

Fedora's Python version migration needs to be coordinated with RHEL.

It is. However it is hard to coordinate a future change with RHEL7 that is kinda designed not to change much.


It isn't with just RHEL7. Customers of RHEL are probably going to want to run their python2 code for years after it is EOL. If something has been written as part of a regulatory compliance (say a plane/car/rocket simulation).. that code is locked for 20 years whether the language below is alive or not. If the code was written for infrastructure it might be 60 years. So as Python became the goto language for science and engineering.. it has also become the language of regulations and other things. RHELn may still need to have python be able to point to python2 because customers need it for reasons we in Fedora or the Python community do not care about. 

From the conversations, this is the part that seems less explored.
 

--
Stephen J Smoogen.