Re: Sunsetting Beam Python 3.8 Support

2024-08-26 Thread Valentyn Tymofieiev via dev
On Mon, Aug 26, 2024 at 11:57 AM Robert Bradshaw wrote: > On Mon, Aug 26, 2024 at 11:22 AM Valentyn Tymofieiev via dev > wrote: > > > > Interesting findings. When researching Dataflow Python usage with > internal telemetry, I see that Python 3.11 has slightly more usage than > Python 3.8. When I

Re: Sunsetting Beam Python 3.8 Support

2024-08-26 Thread Robert Bradshaw via dev
On Mon, Aug 26, 2024 at 11:22 AM Valentyn Tymofieiev via dev wrote: > > Interesting findings. When researching Dataflow Python usage with internal > telemetry, I see that Python 3.11 has slightly more usage than Python 3.8. > When I exclude Dev SDKs (this might also exclude some Google-internal

Re: Sunsetting Beam Python 3.8 Support

2024-08-26 Thread Valentyn Tymofieiev via dev
Interesting findings. When researching Dataflow Python usage with internal telemetry, I see that Python 3.11 has slightly more usage than Python 3.8. When I exclude Dev SDKs (this might also exclude some Google-internal users who use bleeding-edge SDKs), Python 3.8 reaches to the top. If I exclude

Re: Sunsetting Beam Python 3.8 Support

2024-08-26 Thread Jack McCluskey via dev
To Robert Bradshaw's point, I wouldn't necessarily be opposed to pushing out this process to 2.61.0. That does give more time to validate some of the actions changes and let us warn users about the drop in 3.8 support in a release. Admittedly a major motivator for moving off of 3.8 at EoL is so I c

Re: Sunsetting Beam Python 3.8 Support

2024-08-26 Thread Robert Burke
A minor point but often when onboarding, folks will try things verbatim from the website and documentation: https://github.com/search?q=repo%3Aapache%2Fbeam+python3.7+lang%3AMarkdown+&type=code Granted, the most popular combo there was not present in this search, so it's probably not terribly

Re: Sunsetting Beam Python 3.8 Support

2024-08-26 Thread Robert Burke
I'd take care only relying on the most recent release (as much as it supports the consensus point). The most recent beam version is inherently going to have smaller and less consistent numbers, vs N-1 or N-2, since only the most keen or in need updates immediately. On Mon, Aug 26, 2024, 9:27 AM Da

Re: Sunsetting Beam Python 3.8 Support

2024-08-26 Thread Danny McCormick via dev
Was about to respond, Rebo you beat me to it! I agree DockerHub is the right thing to look at since Pypi reporting isn't awesome, I think we should only look at the most recent versions though, since 3.8 will work for old versions forever. For 2.58.0 last month (partial month results), I see: "Re

Re: Sunsetting Beam Python 3.8 Support

2024-08-26 Thread Robert Burke
As an approximation we can use the docker container pulls at least. Py version : Pulls last week 3.8: 7476 3.9: 1,259 3.10: 6169 3.11: 2999 3.12: 241 3.7: 395 3.6: 241 3.4: 156 2.7: 188 But note that any of our automation for 3.8 that pulls containers would impact these result too. I will n

Re: Sunsetting Beam Python 3.8 Support

2024-08-26 Thread Kenneth Knowles
SGTM Incidentally I poked around on pypi for a minute but didn't find even basic download analytics. Do we have data about usage of Python versions? (this is not pushback - I'm all for turning things down on a natural pace (or faster!); I'm just even *more* for having data around it) Kenn On Mon