Remove Python 2.7 support and six.py

[sepeth]

Hello,

This is my first contribution to FoundationDB. I thought I could start from something simple ^-^

This change removes Python 2.7 support and six.py (resolves #11328 and #11329). Most of it is straightforward, such as six.text_type -> str, six.integer_types -> int. OTOH, decisions I made:

• Kept int2byte as it is nicer to read than struct.Struct(">B").pack, and it was used many times.
• As for the tester name, I decided to keep the name "python", but the executable it points to is still "python3". Every other language on the list was without its version, so it made sense this way.
• Deleted most mentions of Python 2.7 as it has been dead for a long time.

I first tested with the class scheduling examples in the tutorial and validated that fdb.__path__ was pointing to the fdb that I modified and installed.

Then, I tested via run_tester_loop.sh & bindingtester.py. This took a bit of time and required some fiddling with sources. But eventually, I got it running, and all python tests have passed. A few issues I had to overcome:

• bindingtester.py is prepending a path to sys.path, which didn't allow me to run run_tester_loop.sh from the source dir.
• bindingtester weren't copied/built into the build tree (due to a check in bindingtester/CMakeLists.txt). I am not sure about the implications of enabling this, but it would be nice if bindingtester is easier to run in case changes made to bindings. I didn't want to make assumptions and changes about this, and wanted to keep this solely for removing Python 2.7 support, but I am happy to look into this in another PR (and happy to hear your suggestions).

Code-Reviewer Section

The general pull request guidelines can be found here.

Please check each of the following things and check all boxes before accepting a PR.

• [X] The PR has a description, explaining both the problem and the solution.
• [X] The description mentions which forms of testing were done and the testing seems reasonable.
• [ ] Every function/class/actor that was touched is reasonably well documented.

For Release-Branches

If this PR is made against a release-branch, please also check the following:

• [ ] This change/bugfix is a cherry-pick from the next younger branch (younger release-branch or main if this is the youngest branch)
• [ ] There is a good reason why this PR needs to go into a release branch and this reason is documented (either in the description above or in a linked GitHub issue)

[foundationdb-ci]

Result of foundationdb-pr-clang-ide on Linux CentOS 7

• Commit ID: 4485534fd92be8b47ffa4fb9f57b91715b4825e2
• Duration 0:23:27
• Result: :white_check_mark: SUCCEEDED
• Error: N/A
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-macos-m1 on macOS Ventura 13.x

• Commit ID: 4485534fd92be8b47ffa4fb9f57b91715b4825e2
• Duration 0:35:04
• Result: :white_check_mark: SUCCEEDED
• Error: N/A
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-clang on Linux CentOS 7

• Commit ID: 4485534fd92be8b47ffa4fb9f57b91715b4825e2
• Duration 0:36:26
• Result: :x: FAILED
• Error: Error while executing command: if python3 -m joshua.joshua list --stopped | grep ${ENSEMBLE_ID} | grep -q 'pass=10[0-9][0-9][0-9]'; then echo PASS; else echo FAIL && exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-macos on macOS Ventura 13.x

• Commit ID: 4485534fd92be8b47ffa4fb9f57b91715b4825e2
• Duration 0:46:41
• Result: :white_check_mark: SUCCEEDED
• Error: N/A
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr on Linux CentOS 7

• Commit ID: 4485534fd92be8b47ffa4fb9f57b91715b4825e2
• Duration 0:54:46
• Result: :x: FAILED
• Error: Error while executing command: if python3 -m joshua.joshua list --stopped | grep ${ENSEMBLE_ID} | grep -q 'pass=10[0-9][0-9][0-9]'; then echo PASS; else echo FAIL && exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-cluster-tests on Linux CentOS 7

• Commit ID: 4485534fd92be8b47ffa4fb9f57b91715b4825e2
• Duration 0:59:44
• Result: :white_check_mark: SUCCEEDED
• Error: N/A
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)
• Cluster Test Logs zip file of the test logs (available for 30 days)

[xis19]

Let's check for the binding correctness in the CI after you changed the code. We have plenty of tests to make sure we do not break things, but still, not enough.

[foundationdb-ci]

Result of foundationdb-pr-clang-ide on Linux CentOS 7

• Commit ID: dc5510af2671ea8a2e87b204945964580b211aea
• Duration 0:22:28
• Result: :white_check_mark: SUCCEEDED
• Error: N/A
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-clang on Linux CentOS 7

• Commit ID: dc5510af2671ea8a2e87b204945964580b211aea
• Duration 0:53:54
• Result: :x: FAILED
• Error: Error while executing command: if python3 -m joshua.joshua list --stopped | grep ${ENSEMBLE_ID} | grep -q 'pass=10[0-9][0-9][0-9]'; then echo PASS; else echo FAIL && exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr on Linux CentOS 7

• Commit ID: dc5510af2671ea8a2e87b204945964580b211aea
• Duration 0:59:19
• Result: :x: FAILED
• Error: Error while executing command: if python3 -m joshua.joshua list --stopped | grep ${ENSEMBLE_ID} | grep -q 'pass=10[0-9][0-9][0-9]'; then echo PASS; else echo FAIL && exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[sepeth]

Hi there, please let me know if there's anything wrong. I see some tests are failing but couldn't be sure if they are related - I see they fail in some other PRs as well.

[jzhou77]

Hi there, please let me know if there's anything wrong. I see some tests are failing but couldn't be sure if they are related - I see they fail in some other PRs as well.

python3 -m joshua.joshua list --stopped failure doesn't seem to be related to the Python changes in this PR (maybe merge with HEAD can resolve some of the failures fixed recently).

I saw some changes for bindingtester, so @xis19 can you make sure bindingtester can still pass joshua test?