I'm wondering if anyone can shed any light on possible roadmaps for transitioning to newer python 3.X in RHEL8/EPEL8. What we have now appears to be:
A module for different pythonXY versions:
python27 2.7 [d] common [d] Python programming language, version 2.7 python36 3.6 [d][e] common [d], build Python programming language, version 3.6
A python3Y base package:
python36.x86_64 3.6.8-2.module+el8.1.0+3334+5cb623d7 python36-debug.x86_64 3.6.8-2.module+el8.1.0+3334+5cb623d7 python36-devel.x86_64 3.6.8-2.module+el8.1.0+3334+5cb623d7 python36-rpm-macros.noarch 3.6.8-2.module+el8.1.0+3334+5cb623d7
But python3- modules, including:
python3-libs.x86_64 3.6.8-15.1.el8 python3-tkinter.x86_64 3.6.8-15.1.el8
And since:
# rpm -E %python3_pkgversion 3
It seems any transition is going to have to be a hard break and/or we're going to need modules. Is there any hope for parallel installable python3Y stacks in RHEL8? Are we just going to have python36 forever?
On 16. 11. 19 3:53, Orion Poplawski wrote:
I'm wondering if anyone can shed any light on possible roadmaps for transitioning to newer python 3.X in RHEL8/EPEL8. What we have now appears to be:
A module for different pythonXY versions:
python27 2.7 [d] common [d] Python programming language, version 2.7 python36 3.6 [d][e] common [d], build Python programming language, version 3.6
A python3Y base package:
python36.x86_64 3.6.8-2.module+el8.1.0+3334+5cb623d7 python36-debug.x86_64 3.6.8-2.module+el8.1.0+3334+5cb623d7 python36-devel.x86_64 3.6.8-2.module+el8.1.0+3334+5cb623d7 python36-rpm-macros.noarch 3.6.8-2.module+el8.1.0+3334+5cb623d7
But python3- modules, including:
python3-libs.x86_64 3.6.8-15.1.el8 python3-tkinter.x86_64 3.6.8-15.1.el8
And since:
# rpm -E %python3_pkgversion 3
It seems any transition is going to have to be a hard break and/or we're going to need modules. Is there any hope for parallel installable python3Y stacks in RHEL8? Are we just going to have python36 forever?
The EL8 Python modules are planned to be parallel installable. That's why the module name is python36, not python or python3.
On 11/16/19 8:25 AM, Miro Hrončok wrote:
On 16. 11. 19 3:53, Orion Poplawski wrote:
I'm wondering if anyone can shed any light on possible roadmaps for transitioning to newer python 3.X in RHEL8/EPEL8. What we have now appears to be:
A module for different pythonXY versions:
python27 2.7 [d] common [d] Python programming language, version 2.7 python36 3.6 [d][e] common [d], build Python programming language, version 3.6
A python3Y base package:
python36.x86_64 3.6.8-2.module+el8.1.0+3334+5cb623d7 python36-debug.x86_64 3.6.8-2.module+el8.1.0+3334+5cb623d7 python36-devel.x86_64 3.6.8-2.module+el8.1.0+3334+5cb623d7 python36-rpm-macros.noarch 3.6.8-2.module+el8.1.0+3334+5cb623d7
But python3- modules, including:
python3-libs.x86_64 3.6.8-15.1.el8 python3-tkinter.x86_64 3.6.8-15.1.el8
And since:
# rpm -E %python3_pkgversion 3
It seems any transition is going to have to be a hard break and/or we're going to need modules. Is there any hope for parallel installable python3Y stacks in RHEL8? Are we just going to have python36 forever?
The EL8 Python modules are planned to be parallel installable. That's why the module name is python36, not python or python3.
Okay, but what does that actually get us in practice? If I have python36 and python38 installed:
- what verion(s) of python3-libs do I have? - what version(s) of python modules from EPEL do I have?
With EPEL7 I can have both python34-blah and python36-blah, but with python3_pkgversion = 3 we just have python3-blah in EPEL8 (currently built for 3.6).
epel-devel@lists.fedoraproject.org