Downgrade to python3.11

[cc-a]

Description

Downgrade from python 3.12 to 3.11. Unfortunately this is necessary for the Kafka work due to a bug with the Kafka client library in 3.12 - dpkp/kafka-python#2412. Whilst we could swap to the alternative python-kafka-ng package this is described as a workaround and the relationship between the 2 is not fully clear.

Type of change

• Documentation (non-breaking change that adds or improves the documentation)
• New feature (non-breaking change which adds functionality)
• Optimization (non-breaking, back-end change that speeds up the code)
• Bug fix (non-breaking change which fixes an issue)
• Breaking change (whatever its nature)

Key checklist

• All tests pass (eg. python -m pytest)
• The documentation builds and looks OK (eg. python -m sphinx -b html docs docs/build)
• Pre-commit hooks run successfully (eg. pre-commit run --all-files)

Further checks

• Code is commented, particularly in hard-to-understand areas
• Tests added or an issue has been opened to tackle that in the future. (Indicate issue here: # (issue))

[dalonsoa]

That's a pity.

It should be flagged in the next meeting - or at some point - as a potential barrier for the long term sustainability of the tool.

[dalonsoa]

Shouldn't this be limited to "<3.12"?

[cc-a]

As this is a tool where deployment will be in a controlled environment it's best to pin against a specific version so we don't have to worry about testing on different versions. That reminds me. Forgot to update the CI.

[cc-a]

Going to merge this now. Be aware @dalonsoa @AdrianDAlessandro @jamesturner246 @TinyMarsh that poetry will complain and make you recreate your environment with python3.11 the next time you do something with dependencies after pulling in the changes. You can use poetry env use /path/to/python3.11 to do so. Sorry for the inconvenience.