Is there a particular reason for the UnifiedInstaller for Plone 4.3.19 not to use the latest Python 2.7 version?
The CentOS server I'm currently working on has still a Python 2.7.5 (at least a so-called one), so I used the --build-python option and was quite surprised to find a Python 2.7.13 to be built.
I changed the install.sh script to use 2.7.18 instead (the very final 2.7 release), and it worked nicely.
(Didn't run any tests yet; no test binaries created by the script, right?)
I'll create a pull request when told which branch to use ...
Is there a particular reason for the UnifiedInstaller for Plone 4.3.19 not to use the latest Python 2.7 version?
The CentOS server I'm currently working on has still a Python 2.7.5 (at least a so-called one), so I used the
--build-pythonoption and was quite surprised to find a Python 2.7.13 to be built.I changed the
install.shscript to use 2.7.18 instead (the very final 2.7 release), and it worked nicely. (Didn't run any tests yet; no test binaries created by the script, right?) I'll create a pull request when told which branch to use ...