HPCC-22880 Default to python3

[richardkchapman]

Python2 is reaching end-of-life

Signed-off-by: Richard Chapman rchapman@hpccsystems.com

Type of change:

• This change is a bug fix (non-breaking change which fixes an issue).
• This change is a new feature (non-breaking change which adds functionality).
• This change improves the code (refactor or other change that does not change the functionality)
• This change fixes warnings (the fix does not alter the functionality or the generated code)
• This change is a breaking change (fix or feature that will cause existing behavior to change).
• This change alters the query API (existing queries will have to be recompiled)

Checklist:

• My code follows the code style of this project.
  • My code does not create any new warnings from compiler, build system, or lint.
• The commit message is properly formatted and free of typos.
  • The commit message title makes sense in a changelog, by itself.
  • The commit is signed.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly, or...
  • I have created a JIRA ticket to update the documentation.
  • Any new interfaces or exported functions are appropriately commented.
• I have read the CONTRIBUTORS document.
• The change has been fully tested:
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • I have checked that this change does not introduce memory leaks.
  • I have used Valgrind or similar tools to check for potential issues.
• I have given due consideration to all of the following potential concerns:
  • Scalability
  • Performance
  • Security
  • Thread-safety
  • Premature optimization
  • Existing deployed queries will not be broken
  • This change fixes the problem, not just the symptom
  • The target branch of this pull request is appropriate for such a change.
• There are no similar instances of the same problem that should be addressed
  • I have addressed them here
  • I have raised JIRA issues to address them separately
• This is a user interface / front-end modification
  • I have tested my changes in multiple modern browsers
  • The component(s) render as expected

Smoketest:

• Send notifications about my Pull Request position in Smoketest queue.
• Test my draft Pull Request.

Testing:

[hpcc-jirabot]

https://track.hpccsystems.com/browse/HPCC-22880
Jira updated

[richardkchapman]

@JamesDeFabia Any documentation impact?

[richardkchapman]

@Michael-Gardner Please review

[HPCCSmoketest]

Automated Smoketest: ✅
OS: centos 7.6.1810 (Linux 3.10.0-327.28.3.el7.x86_64)
GCC:gcc (GCC) 7.3.1 20180303 (Red Hat 7.3.1-5)
Sha: 401560a
Build: success
Build: success
Install HPCC Platform
HPCC Start: OK

Unit tests result:

Test	total	passed	failed	errors	timeout	elaps
unittest	116	116	0	0	0	36 sec
wutoolTest(Dali)	19	19	0	0	0	2 sec
wutoolTest(Cassandra)	19	19	0	0	0	8 sec

Regression test result:

phase	total	pass	fail	elaps
setup (hthor)	11	11	0	25 sec (00:00:25)
setup (thor)	11	11	0	47 sec (00:00:47)
setup (roxie)	11	11	0	17 sec (00:00:17)
test (hthor)	861	861	0	193 sec (00:03:13)
test (thor)	785	785	0	706 sec (00:11:46)
test (roxie)	936	936	0	420 sec (00:07:00)

HPCC Stop: OK
Time stats:

Prep time	Build time	Package time	Install time	Start time	Test time	Stop time	Summary
29 sec (00:00:29)	256 sec (00:04:16)	0 sec (00:00:00)	3 sec (00:00:03)	20 sec (00:00:20)	1654 sec (00:27:34)	21 sec (00:00:21)	1983 sec (00:33:03)

[Michael-Gardner]

@richardkchapman looks good