Conversation
|
Just for the record: It seems like this is currently only blocked by https://github.com/qwj/python-proxy not being compatible with Python 3.11. The library seems to be unmaintained, there is an open PR for quite a while: qwj/python-proxy#163 |
|
what is the library used for @alexrashed ? |
|
It is the base for |
7a57c4f to
34a51e0
Compare
|
I just rebased this PR and cherry-picked f1da6ac from #8577. In another commit I removed all installations of SASL lib OS packages. Packages are moving to thobbs/pure-sasl due to cloudera/python-sasl#30, and the package should not be necessary anymore. |
796ed61 to
dac4c8d
Compare
|
It seems like the Podman tests might be a bit flaky (only the first Edit: Yes, the tests also fail on master currently, they are unrelated and should be fixed in another PR. |
dac4c8d to
b1ca038
Compare
6a7c7af to
41b04b0
Compare
41b04b0 to
157afc1
Compare
b39c93d to
86aafe4
Compare
86aafe4 to
a7f3fcf
Compare
7568daa to
56f9970
Compare
56f9970 to
40a9763
Compare
40a9763 to
99c7686
Compare
alexrashed
left a comment
There was a problem hiding this comment.
Awesome! We're finally there! Let's get this over the line! 🚀 ![]()
Motivation
This PR contains all changes necessary to upgrade our Python version for the runtime from 3.10 to 3.11.
Changes
libsnappy-devinstead oflibsasl2-devwhen running against Pro (see changes there for a detailed explanation)./usr/lib/localstack/python-packages/lib/python3.11/site-packages).python-proxy- is not maintained and not compatible with 3.11).Impact
This PR only updates the runtime version of LocalStack itself. The LocalStack CLI will still be compatible with Python 3.7+.
However, Python Initialization Hooks and LocalStack Extensions will then run in a Python 3.11 environment instead of Python 3.10.
TODO: