thanks, email sent! let me know if it got screwed up. I don't have a Pony login, so I used the "reply via mail client" button.
-chad On Thu, Sep 19, 2019 at 1:44 PM Valentyn Tymofieiev <valen...@google.com> wrote: > There was a previous thread on this topic[1]. Should we continue this > conversation there? > > https://lists.apache.org/thread.html/eba6caa58ea79a7ecbc8560d1c680a366b44c531d96ce5c699d41535@%3Cdev.beam.apache.org%3E > > On Thu, Sep 19, 2019 at 12:55 PM Chad Dombrova <chad...@gmail.com> wrote: > >> 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 >> >>
