Hi Mika, Thank you very much for initiating this discussion. We did not have very strict rules for deprecating Python versions before, but we usually chose to start deprecation about a year after EOF and stop supporting the Python version in the next Flink version. The reason why we started deprecation one year after EOF is to give users enough time to upgrade their Python versions. Therefore, it will not be a big problem to drop only one Flink version from my side, and this can reduce the pressure of maintaining too many Python versions.
As far as I know, Python users will upgrade their Python versions more frequently, the migration cost is not that high, and Python versions after Python 3.9 will be relatively more mature (many CPython core C APIs are relatively stable in Python 3.9) Best, Xingbo Mika Naylor <m...@autophagy.io.invalid> 于2025年5月26日周一 22:55写道： > Hi all, > > I recently wanted to look into using the new dependency groups mechanism > for centralising testing/development requirements in one place in a > consistent format, rather than scattered in various places. I opened > FLINK-37775 to reflect this, but had to drop it as it's only a feature in > new versions of pip, and new pip versions are no longer being released for > our minimum Python version, 3.8. > > 3.8 is officially end of life as of last year[1], but is still used[2]. > With 3.8 at EOL, and 3.9 reaching it end of this year, I wanted to ask for > feedback on whether: > > • We have some sort of policy or intuition around deprecating/dropping > support for Python versions to make maintenance burden a little easier, and > whether this should be based on languages reaching eol, wider language > version usage or whether we have insight into what python versions those on > the latest Flink versions are using. > • Whether we should deprecate the version first (like in FLINK-28195[3]), > and how many minor versions this deprecation should exist for before > dropping altogether (just one?) > Kind regards, > Mika > > [1] https://devguide.python.org/versions/ > [2] https://w3techs.com/technologies/history_details/pl-python/3 > [3] https://issues.apache.org/jira/browse/FLINK-28195
