WIP python 3.12 upgrade

[chris48s]

And so the "upgrade all the things" project rumbles on.

[chris48s]

It looks like there are 2 places we care about using this package:

1. In our applications (which are all now running on python 3.12, across the board)
2. In AWS CloudShell.

TIL AWS CloudShell. TI also L that the most recent python version available in the Amazon Linux 2023 repository is still python 3.11. Obviously there are other ways to get python on there (pyenv, uv, etc) but it seems like the lowest friction thing to do here is say we are compatible with >=3.11 and leave the instructions in https://github.com/DemocracyClub/dc_logging/blob/main/dc_logging_legacy_import/README.md#running-from-aws-cloudshell as they are for now.

I think we can live with the test suite only being run against 3.12 though. Does that seem right to you?

[chris48s]

Suspect this one might end up sitting around open for a bit, so some notes:

I tried deploying this to the dev account. When deployed to dev I can log a message and the log pops up in the S3 bucket as expected. (I've now rolled those commits back). The code works fine on python 3.12. It is the mocking that is causing the test failure.

I managed to track down the reason for the test failure to

error running docker: 404 Client Error for http+docker://localhost/v1.43/images/create?tag=python3.12&fromImage=lambci%2Flambda: Not Found ("manifest for lambci/lambda:python3.12 not found: manifest unknown: manifest unknown")

I've pushed 38c5032 which will now log that error instead of swallowing it.

I've also raised an issue upstream over on the moto repo getmoto/moto#8236 Lets see where that goes..