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 <http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/VOTE-Drop-Python-2-support-for-1-10-tt33962.html> > 在 2019年10月12日，下午5:44，jincheng sun <sunjincheng...@gmail.com> 写道： > > Hi Dian, > > I think it's better to bring up the VOTE for this proposal. Then push this > forward.:) > > Thanks, > Jincheng > > Timo Walther <twal...@apache.org> 于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 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 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 support are: >>> 1. Maintaining Python 2/3 compatibility is a burden and it makes the >> code complicate as Python 2 and Python 3 is not compatible. >>> 2. There are many features which are only available in Python 3.x such >> as Type Hints[5]. We can only make use of this kind of features after >> dropping the Python 2 support. >>> 3. Flink-python depends on third-part projects, such as Apache Beam (may >> add more dependencies such as pandas, etc in the near future), it's not >> possible to upgrade them to the latest version once they drop the Python 2 >> support. >>> >>> Here are the options we have: >>> 1. Drop Python 2 support in 1.10: >>> As flink-python module is a new module added since 1.9.0 and so dropping >> Python 2 support at the early stage seems a good choice for us. >>> 2. Deprecate Python 2 in 1.10 and drop its support in 1.11: >>> As 1.10 is planned to be released around the beginning of 2020. This is >> also aligned with the official Python 2 support. >>> >>> Personally I prefer option 1 as flink-python is new module and there is >> no much history reasons to consider. >>> >>> Looking forward to your feedback! >>> >>> Regards, >>> Dian >>> >>> [1] https://pythonclock.org/ <https://pythonclock.org/> >>> [2] https://python3statement.org/ <https://python3statement.org/> >>> [3] >> https://spark.apache.org/news/plan-for-dropping-python-2-support.html < >> https://spark.apache.org/news/plan-for-dropping-python-2-support.html> >>> [4] >> https://lists.apache.org/thread.html/eba6caa58ea79a7ecbc8560d1c680a366b44c531d96ce5c699d41535@%3Cdev.beam.apache.org%3E >> < >> https://lists.apache.org/thread.html/eba6caa58ea79a7ecbc8560d1c680a366b44c531d96ce5c699d41535@%3Cdev.beam.apache.org%3E >>> >>> [5] >> https://stackoverflow.com/questions/32557920/what-are-type-hints-in-python-3-5 >> < >> https://stackoverflow.com/questions/32557920/what-are-type-hints-in-python-3-5 >>> >> >> >>
