Considering Python 2.6 support

[JumpingYang001]

I saw @alinbalutoiu checked in Python 2.6 support in README, our build system are based on system with python2.7 default, so if we want to support Python 2.6, we might need to change build system again?

List python default version for all platforms:

Platforms	Python default version
centos5 x64	2.4.3
centos5 x86	2.4.3
centos6x64	2.6.5
centos6x86	2.6.5
centos7 x64	2.7.5
oracle5 x64	2.4.3
oracle5 x86	2.4.3
oracle6 x64	2.6.5
oracle6 x86	2.6.5
oracle7 x64	2.7.5
Sles10 x64	2.4.2
Sles10 x86	2.4.2
Sles11 x64	2.6
Sles11 x86	2.6
Sles12 x64	2.7.7
Rhel5 x64	2.4.3
Rhel5 x86	2.4.3
Rhel6 x64	2.6.5
Rhel6 x86	2.6.5
Rhel7 x64	2.7.5
Rhel7PPC	2.7.5
debian6 x64	2.6.6
debian6 x86	2.6.6
debian7 x64	2.7.3
debian7 x86	2.7.3
debian8 x64	2.7.9
debian8 x86	2.7.9
Debian9 x64	2.7.13
Ubuntu12.4lts x64	2.7.3
Ubuntu12.4lts x86	2.7.3
Ubuntu14.4lts x64	2.7.6
Ubuntu14.4lts x86	2.7.6
Ubuntu16.4lts x64	2.7.11+
Ubuntu16.4lts x86	2.7.11+

[JumpingYang001]

From the code, I think here is what for python 2.6 support:

1. User need to run ./configure --python-version=2.6 when building.
2. Then the built product(rpm/deb package) only support python2.6 for running, is it correct?

[alinbalutoiu]

@JumpingYang001 I marked the Python versions as beta support.
Indeed, you have to run ./configure with --python-version=<python_version> in order to switch to a different python version. The packages will be built only for that specific Python version, as a result if you check you will see that the package name will also contain "Python-<python_version>" which corresponds to the Python version for which it was built.
To answer your initial question, there is no need to change the build system again, if you want to build for a specific Python version, it just needs to be present on the system, you can have multiple versions of Python on a single system.