Upgrading to Python 3

[jakirkham]

Is your feature request related to a problem? Please describe.

It appears that Python 2.6 is used in some places like here and here. However Python 2.6 has long since reach its EOL. Not to mention Python 2.7 will not be supported further in the new year.

Describe the solution you'd like

It would be good to move all scripts to support Python 3.

Describe alternatives you've considered

A good compromise would be to get all of the scripts to support Python 2/3, which should continue to work after Python 2 reaches its EOL.

Additional context

Here's the Python EOL guide.

[cdunn2001]

I've deleted makerelease.py (#1083). Problem solved! 😄

@hjmjohnson, Could you take care of py2.6 in CMake?

• jsoncpp/src/jsontestrunner/CMakeLists.txt

  Line 1 in aebc7fa

  find_package(PythonInterp 2.6)

Note: We actually run jsontestrunner via Meson in TravisCI, using python3, so I don't think the python version actually matters.

... Oh, we actually still use CMake -- in the AppVeyor build. I think that runs jsontestrunner too -- yes, jsontestrunner_exe.vcxproj -- so we have a test for whatever change you make. I just hate dealing with CMake at all. I wonder if we could use Meson in AppVeyor.

[hjmjohnson]

OK. Moving to python3 only for support.