Thank you for the feedback and guidance everyone :) I'll open a PR to drop
Python 3.8 support.
Kind regards,
Mika
Solid +1 for dropping instead of deprecate.
Best,
Ferenc
On Wednesday, May 28th, 2025 at 07:12, Gabor Somogyi
wrote:
>
>
> Hi Mika,
>
> +1 to drop and not just deprecate from my side.
>
> BR,
> G
>
>
> On Wed, May 28, 2025 at 7:06 AM Dian Fu dian0511...@gmail.com wrote:
>
> > Hi Mika,
Hi Mika,
+1 to drop and not just deprecate from my side.
BR,
G
On Wed, May 28, 2025 at 7:06 AM Dian Fu wrote:
> Hi Mika,
>
> Thanks for bringing up this discussion.
>
> Regarding dropping support of Python 3.8: +1 for this. Since we will
> add support for Python 3.12 in Flink 2.1[1], this mea
Hi Mika,
Thanks for bringing up this discussion.
Regarding dropping support of Python 3.8: +1 for this. Since we will
add support for Python 3.12 in Flink 2.1[1], this means we need to
maintain 5 Python versions if we still support Python 3.8. Considering
that 3.8 is already EOL and the issue you
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 deprec
+1 I'd support dropping EOL python versions from the next / latest flink
version. Users who end up on older python versions will need to spend time
to update their flink versions and can always continue using older versions
until they are ready to upgrade. Dropping old versions on the master branch
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
