Yeah, we'll probably have to upgrade to Py3 compatibility eventually, but we've got lots of other stuff on our plate for now.
We actually do use cx_Freeze to build our services, so in theory it's only the version of Python in our build environment that matters. Realistically, though, adding a custom Python version that's not part of the baseline RHEL distro would add overhead and hassle to our workflow and requirements right now, and there's no immediate reason to move away from Py2.7 atm.
Yeah, we'll probably have to upgrade to Py3 compatibility eventually, but we've got lots of other stuff on our plate for now.
Yeah I totally get it, that's why I suggested for people to initiate a conversation about it in their own teams. 2020 is not that far. Python 2.7 is battle tested but having no support or security fixes can be an issue if you have customer facing apps.
Realistically, though, adding a custom Python version that's not part of the baseline RHEL distro would add overhead and hassle to our workflow and requirements right now
I agree with the hassle :-)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yeah, we'll probably have to upgrade to Py3 compatibility eventually, but we've got lots of other stuff on our plate for now.
We actually do use
cx_Freeze
to build our services, so in theory it's only the version of Python in our build environment that matters. Realistically, though, adding a custom Python version that's not part of the baseline RHEL distro would add overhead and hassle to our workflow and requirements right now, and there's no immediate reason to move away from Py2.7 atm.Yeah I totally get it, that's why I suggested for people to initiate a conversation about it in their own teams. 2020 is not that far. Python 2.7 is battle tested but having no support or security fixes can be an issue if you have customer facing apps.
I agree with the hassle :-)