Re: [DISCUSS] Drop Python 2 support for 1.10

Thanks Jincheng for the remind and everyone for joining the discussion. I have started the vote thread in [1]. Thanks, Dian [1] http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/VOTE-Drop-Python-2-support-for-1-10-tt33962.html

Re: [DISCUSS] Drop Python 2 support for 1.10

Hi Dian, I think it's better to bring up the VOTE for this proposal. Then push this forward.:) Thanks, Jincheng Timo Walther 于2019年10月10日周四 下午8:07写道： > I also heard from other companies that upgrading to Python 3 is in > progress for data teams. > > +1 for simplifying the code base with option

Re: [DISCUSS] Drop Python 2 support for 1.10

I also heard from other companies that upgrading to Python 3 is in progress for data teams. +1 for simplifying the code base with option 1). Thanks, Timo On 08.10.19 16:34, Dian Fu wrote: Hi everyone, I would like to propose to drop Python 2 support(Currently Python 2.7, 3.5, 3.6, 3.7 are a

Re: [DISCUSS] Drop Python 2 support for 1.10

Thanks everyone for your reply. So far all the reply tend to option 1 (dropping Python 2 support in 1.10) and will continue to hear if there are any other opinions. @Jincheng @Hequn, you are right, things become more complicate if dropping Python 2 support is performed after Python UDF has b

Re: [DISCUSS] Drop Python 2 support for 1.10

Thanks for bringing this up Dian. Since python 2.7 support was added in 1.9.0 and would be EOL near the planned release time for 1.10, I could see a good reason to take option 1. Please remember to add an explicit release note and would be better to send a notification in user ML about the plan t

Re: [DISCUSS] Drop Python 2 support for 1.10

+1 Hequn Cheng 于2019年10月9日周三 上午11:07写道： > Hi Dian, > > +1 to drop Python 2 directly. > > Just as @jincheng said, things would be more complicated if we are going to > support python UDFs. > The python UDFs will introduce a lot of python dependencies which will also > drop the support of Python 2

Re: [DISCUSS] Drop Python 2 support for 1.10

Hi Dian, +1 to drop Python 2 directly. Just as @jincheng said, things would be more complicated if we are going to support python UDFs. The python UDFs will introduce a lot of python dependencies which will also drop the support of Python 2, such as beam, pandas, pyarrow, etc. Given this and Pyth

Re: [DISCUSS] Drop Python 2 support for 1.10

Hi Dian， Thanks for bringing this discussion! In Flink 1.9 we only add Python Table API mapping to Java Table API(without Python UDFs), there no special requirements for Python version, so we add python 2,7 support. But for Flink 1.10, we add the Python UDFs support, i.e., user will add more pyth

[DISCUSS] Drop Python 2 support for 1.10

Hi everyone, I would like to propose to drop Python 2 support(Currently Python 2.7, 3.5, 3.6, 3.7 are all supported in Flink) as it's coming to an end at Jan 1, 2020 [1]. A lot of projects [2][3][4] has already stated or are planning to drop Python 2 support. The benefits of dropping Python 2