HCD-190: Upgrade internal pyhon driver to 3.29.2

[szymon-miezal]

What is the issue

The old internal python driver disallows using Python 3.12 in cqlsh.

What does this PR fix and why was it fixed

• Replace cassandra-driver-internal-only-3.26.0 with 3.29.2
• Update cqlsh and cqlsh.py to support the new driver version
• Remove obsolete Python 2.7, 3.7 Docker configurations, update 3.8 Dockerfile
• Add Python 3.12 Docker configuration support
• Update requirements.txt and test configurations
• In ports the work done under CASSANDRA-19245, CASSANDRA-17417 and CASSANDRA-18354

CNDB PR: https://github.com/riptano/cndb/pull/15198.

[github-actions]

Checklist before you submit for review

• This PR adheres to the Definition of Done
• Make sure there is a PR in the CNDB project updating the Converged Cassandra version
• Use NoSpamLogger for log lines that may appear frequently in the logs
• Verify test results on Butler
• Test coverage for new/modified code is > 80%
• Proper code formatting
• Proper title for each commit staring with the project-issue number, like CNDB-1234
• Each commit has a meaningful description
• Each commit is not very long and contains related changes
• Renames, moves and reformatting are in distinct commits
• All new files should contain the DataStax copyright header instead of the Apache License one

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[szymon-miezal]

Butler report looks ok after addressing the regressions: http://butler-stargazer.aws.dsinternal.org/#/ci/upstream/compare/ds-cassandra-pr-gate/HCD-190/to/ds-cassandra-build-nightly/main.

[michaelsembwever]

Can you update the commit message to reference those CASSANDRA tickets. This makes life easier for the CC rebaser (e.g. knowing whether they should rebase the commit or throw it away).

[tiagomlalves]

I agree with Mick on adding the C* tickets.
I've added a minor suggestion. Approving ticket as there's not need for further review rounds.

[tiagomlalves]

Potentially we could remove the try clause as this was meant to support older Python versions which we no longer support. I wonder if there aren't more such cases.

[adelapena]

Looks good to me, but I think we should update:

• The README.asc requirements section.
• This check in cqlsh.py.
• Maybe this section about requirements in the old doc, although I'm not sure we maintain that anymore.

Also, there are multiple CircleCI jobs using Python 2.7 that we should remove. But, since I think we are not using CircleCI anymore, probably we will be fine with a followup ticket to remove those jobs. Or perhaps even the entire CircleCI config?

[adelapena]

@szymon-miezal Do we have a companion CNDB PR to verify that this doesn't break something there?

[szymon-miezal]

@szymon-miezal Do we have a companion CNDB PR to verify that this doesn't break something there?

I did create https://github.com/riptano/cndb/pull/15198 for that purpose, it looks somewhat ok, I mean, the failures seem unrelated but a CNDB-trained eye would be appreciated on it for sure.

[adelapena]

@szymon-miezal Do we have a companion CNDB PR to verify that this doesn't break something there?

I did create riptano/cndb#15198 for that purpose, it looks somewhat ok, I mean, the failures seem unrelated but a CNDB-trained eye would be appreciated on it for sure.

Thanks, I've just approved the CNDB PR. It will need to be updated after merging this PR.

[adelapena]

I think Python 2.7 doesn't work at all now. Cqlsh will immediately fail with a syntax error before ever reaching this check. So I think we can remove the entire maybe_warn_py2 check and its associated test, test_warn_py2.

[szymon-miezal]

That's a good point. Honestly I wanted to keep this test and see whether it will break in CI but then I realise given https://jenkins-stargazer.aws.dsinternal.org/job/ds-cassandra-pr-gate/job/PR-1960/9/testReport/cqlshlib.python3.8.jdk11.no-cython.x86_64.test.test_cqlsh_output/TestCqlshOutput/ isn't run against python 2.7 (as the config has been removed) it won't be run at all.
And yes you are right, it will fail much earlier in the call-stack so it doesn't make much sense to keep it.

[szymon-miezal]

It seems the test_no_warn_py3 would serve little value after the deletion of maybe_warn_py2, I think it would make sense to remove it too as part of this little rework.

[adelapena]

Agree, that one can be deleted too.

[szymon-miezal]

I found apache@768bdff, which I figure shall be incorporated as well as part of this effort (given the current state of the patch removes python 2.7 support).

[szymon-miezal]

The latest commit broke CI, I need to fix it.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cassci-bot]

❌ Build ds-cassandra-pr-gate/PR-1960 rejected by Butler

---

1 regressions found
See build details here

---

Found 1 new test failures

Test	Explanation	Runs	Upstream
o.a.c.sensors.SensorsReadTest.BeforeFirstTest	NEW	🔴⚪	0 / 2

---

Found 1 known test failures

[szymon-miezal]

It turns out to be blocked by https://issues.apache.org/jira/browse/CASSANDRA-20053 due to the asyncore removal.
I am going to put it back into the draft stage before the tackle the blocker.