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.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
epel-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
