Thanks Gabor for looking into it. It sounds reasonable to me as well. +1
On Sun, Sep 3, 2023 at 5:44 PM Márton Balassi <balassi.mar...@gmail.com> wrote: > Hi Gabor, > > Thanks for bringing this up. Similarly to when we dropped Python 3.6 due to > its end of life (and added 3.10) in Flink 1.17 [1,2], it makes sense to > proceed to remove 3.7 and add 3.11 instead. > > +1. > > [1] https://issues.apache.org/jira/browse/FLINK-27929 > [2] https://github.com/apache/flink/pull/21699 > > Best, > Marton > > On Fri, Sep 1, 2023 at 10:39 AM Gabor Somogyi <gabor.g.somo...@gmail.com> > wrote: > > > Hi All, > > > > I've analyzed through part of the pyflink code and found some improvement > > possibilities. > > I would like to hear voices on the idea. > > > > Intention: > > * upgrade several python related versions to eliminate end-of-life issues > > and keep up with bugfixes > > * start to add python arm64 support > > > > Actual situation: > > * Flink supports the following python versions: 3.7, 3.8, 3.9, 3.10 > > * We use miniconda 4.7.10 (python package management system and > environment > > management system) which supports the following python versions: 3.7, > 3.8, > > 3.9, 3.10 > > * Our python framework is not supporting anything but x86_64 > > > > Issues: > > * Python 3.7.17 is the latest security patch of the 3.7 line. This > version > > is end-of-life and is no longer supported: > > https://www.python.org/downloads/release/python-3717/ > > * Miniconda 4.7.10 is released on 2019-07-29 which is 4 years old already > > and not supporting too many architectures (x86_64 and ppc64le) > > * The latest miniconda which has real multi-arch feature set supports the > > following python versions: 3.8, 3.9, 3.10, 3.11 and no 3.7 support > > > > Suggestion to solve the issues: > > * In 1.19 drop python 3.7 support and upgrade miniconda to the latest > > version which opens the door to other platform + python 3.11 support > > > > Please note python 3.11 support is not initiated/discussed here. > > > > BR, > > G > > >
