Bug 1875817
Summary: | RFE: add collection for Python 3.7 | ||
---|---|---|---|
Product: | Red Hat Software Collections | Reporter: | Sahil thakare <sthakare> |
Component: | distribution | Assignee: | Brian Gollaher <bgollahe> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rh-python38 | CC: | kanderso, pviktori, torsava |
Target Milestone: | alpha | Keywords: | FutureFeature |
Target Release: | 3.6 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-10-12 10:05:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sahil thakare
2020-09-04 13:04:59 UTC
This is not a bug in the rh-python38 collection, but a request to add new softwarte to RHEL. I'm reassigning it to distribution. Adding a new collection is lot of work in packaging, QA and support. I'm not familiar with py4j; what would it take to update it to support Python 3.8 instead? Hello Team, Thanks for your reply, For more information on py4j,Please refer this documentation: https://www.py4j.org/install.html {Py4J is a library written in Python and Java. Currently, Py4J has been tested with Python 2.7, 3.4, 3.5, 3.6, and 3.7. } We have tried to install the dependancy and packages on runtime however it fails with following error. ~~~~~~~~~~~~~~~~~~~ py4j.protocol.Py4JError: org.apache.spark.api.python.PythonUtils.isEncryptionEnabled does not exist in the JVM ~~~~~~~~~~~~~~~~~~~ As per cu, ~~~~~~~~~~~ We would not be able to use the python 3.8 even after customizing with all the modules and dependent libraries because the py4j will not support python 3.8 image yet. We would appreciate having python 3.7 image instead of customizing 3.8. ~~~~~~~~~~~ Please help to progress on this case. Regards, Sahil Thakare Hi Sahil, can the customer use the Python 3.6 collection? It's going EOL soon, but we are working to keep it up to date until that point, and it could be useful after as well. As mentioned above, adding a new collection is an immense amount of work. I'm not sure if it's realistic only to add a specific *old* version of Python, which would EOL soon anyway. And RHEL7 is now in the Maintenance Support 2 phase. Alternatively, the customer could migrate to RHEL8 where Python 3.6 will be supported for the whole lifecycle. |