Probably nobody develop for them now. Nobody creates new images for them. The code could be simplified.
Before doing so it would be nice to:
- Get usage statistics by version to estimate the impact.
- Decide the way how we handle unsupported versions.
Nowadays libraries are expected to be typed.
It's better to do massive changes after autoformatting.
We have a lot of problems in tests, they are hard to read. It's easier to fix the with pytest
s fixtures and pytest-asyncio
.
It's better to do massive changes after autoformatting.
- The current image doesn't seem to work for kafka 3.
- No access to Docker Hub account. Probably we can move images to GitHub?
Some of them are not supported, we already have problems with python-snappy in Python 3.11.
One probable candidate is cramjam could replace them all. According to download statistics it's much more popular, than aiokafka itself.
Both direct invocation of setup.py and setuptools are effectively deprecated. The modern approach is to use pyproject.toml
I personally prefer hatch
. But we have to find out if it plays well with cython.
We already get warnings for them:
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
We need to update instruction and keep CHANGES
directory. Otherwise supporters don't understand what to do.
Exceptions for some error codes are missing (need update, but this will
eventually break anyway). We raise UnknownError
exception in this case,
but then it's the error code of response is lost.