Hi all, I saw it mentioned on another thread that Beam will drop python2 support by the end of the year, and I'd like to voice my concern over this timeline. As far as I can tell, Beam's support for python3 is brand new, and based on the master Jira ticket on this topic [1], there are still at least a dozen *known* issues remaining to be resolved. If we assume it takes another month to resolve all of those, and python2 support is dropped at the end of the year, that leaves a window of barely over 2 months where Beam is fully working for both python versions. I think that will be an uncomfortably short window for some users to transition their production pipelines to Beam on python3, my company included. Of course, users can choose to stay on older versions, but with so many important features still under active development (portability, expansion, external IO transforms, schema coders) and new versions of executors tied to the Beam source, staying behind is not really an option for many of us.
So I'm hoping we could extend support for python2 for a bit longer, if possible. I'm curious who is using Beam on python3 in production, and for which runners? thanks, -chad [1] https://issues.apache.org/jira/browse/BEAM-1251
