Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-06-08 Thread Richard van der Hoff
On 08/06/2020 08:04, Glyph wrote: > I'm going to start here by saying: I agree with almost all of what you wrote, but at the end of the day, I don't get to determine our customers' policies. You can try to explain to them why their policies are misguided, but particularly when you're

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-06-08 Thread Glyph
> On May 28, 2020, at 8:31 AM, Erik Johnston wrote: > > > On 23/05/2020 06:39, Glyph wrote: >> >>> On May 19, 2020, at 1:52 AM, Richard van der Hoff >> > wrote: >>> >>> On 16/05/2020 06:56, Glyph wrote: > On May 15, 2020, at 8:40 PM, Craig

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-06-03 Thread Glyph
> On May 28, 2020, at 3:13 PM, Tom Most wrote: > > On Fri, May 22, 2020, at 10:54 PM, Glyph wrote: >> So, pidfd's cool, we should totally use it. Also we should use posix_spawn >> and maybe some other stuff too. But I wonder if there's any heuristic we >> could use to speed up our current

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-28 Thread Tom Most
On Fri, May 22, 2020, at 10:54 PM, Glyph wrote: > So, pidfd's cool, we should totally use it. Also we should use posix_spawn > and maybe some other stuff too. But I wonder if there's any heuristic we > could use to speed up our current strategy, like ordering the to-reap list by > putting

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-22 Thread Glyph
> On May 19, 2020, at 11:14 AM, Tom Most wrote: > > On Tue, May 19, 2020, at 5:41 AM, Jean-Paul Calderone wrote: >> On Tue, May 19, 2020 at 8:33 AM Barry Scott > > wrote: >> Why not waitpid for all children (pid=0 or pid=-1) in a single call? >> >> Because

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-22 Thread Glyph
> On May 19, 2020, at 5:41 AM, Jean-Paul Calderone > wrote: > > On Tue, May 19, 2020 at 8:33 AM Barry Scott > wrote: > On Monday, 18 May 2020 22:21:16 BST Tom Most wrote: > > > > > If looking improve process management in Twisted, I think that the > >

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-22 Thread Glyph
> On May 19, 2020, at 1:52 AM, Richard van der Hoff wrote: > > On 16/05/2020 06:56, Glyph wrote: >> >> >>> On May 15, 2020, at 8:40 PM, Craig Rodrigues >> > wrote: >>> >>> Maybe it would be OK to do one more release of Twisted and announce that as >>> the last

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-19 Thread Tom Most
On Tue, May 19, 2020, at 5:41 AM, Jean-Paul Calderone wrote: > On Tue, May 19, 2020 at 8:33 AM Barry Scott > wrote: >> Why not waitpid for all children (pid=0 or pid=-1) in a single call? > > Because then you might reap a child process someone launched with a different > API - eg the Python

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-19 Thread Jean-Paul Calderone
On Tue, May 19, 2020 at 8:33 AM Barry Scott wrote: > On Monday, 18 May 2020 22:21:16 BST Tom Most wrote: > > > > > If looking improve process management in Twisted, I think that the > > lowest-hanging fruit is to watch children with pidfd, rather than reaping > > all children on SIGCHLD. This

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-19 Thread Barry Scott
On Monday, 18 May 2020 22:21:16 BST Tom Most wrote: > On Sun, May 17, 2020, at 12:22 PM, Glyph wrote: > >> In the one case that may be complicated I think that pinning Twisted will > >> be acceptable, since the service in question is a process supervisor > >> without direct external exposure.> >

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-19 Thread Richard van der Hoff
On 16/05/2020 06:56, Glyph wrote: On May 15, 2020, at 8:40 PM, Craig Rodrigues > wrote: Maybe it would be OK to do one more release of Twisted and announce that as the last release supporting Python 3.5, before dropping support? Yeah; whenever we drop a

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-18 Thread Tom Most
On Sun, May 17, 2020, at 12:22 PM, Glyph wrote: >> In the one case that may be complicated I think that pinning Twisted will be >> acceptable, since the service in question is a process supervisor without >> direct external exposure. > Well in that case I'll just do my best to add lots of

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-17 Thread Glyph
> On May 17, 2020, at 12:10 PM, Tom Most wrote: > > On Sun, May 17, 2020, at 11:31 AM, Glyph wrote: >> >>> On May 16, 2020, at 3:12 PM, Tom Most >> > wrote: >>> I'm (unfortunately) still shipping some Twisted apps on Ubuntu 16.04's >>> Python 3.5. However, I am fine

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-17 Thread Tom Most
On Sun, May 17, 2020, at 11:31 AM, Glyph wrote: > >> On May 16, 2020, at 3:12 PM, Tom Most wrote: >> I'm (unfortunately) still shipping some Twisted apps on Ubuntu 16.04's >> Python 3.5. However, I am fine with dropping Python 3.5 support. I think >> it's certainly worth it for variable

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-17 Thread Glyph
> On May 16, 2020, at 3:12 PM, Tom Most wrote: > > > On Fri, May 15, 2020, at 10:56 PM, Glyph wrote: >> >> >>> On May 15, 2020, at 8:40 PM, Craig Rodrigues >> > wrote: >>> >>> Maybe it would be OK to do one more release of Twisted and announce that as >>> the

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-16 Thread Tom Most
I'm (unfortunately) still shipping some Twisted apps on Ubuntu 16.04's Python 3.5. However, I am fine with dropping Python 3.5 support. I think it's certainly worth it for variable annotations and contextvars. ---Tom On Fri, May 15, 2020, at 10:56 PM, Glyph wrote: > > >> On May 15, 2020, at

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-15 Thread Glyph
> On May 15, 2020, at 8:40 PM, Craig Rodrigues wrote: > > Maybe it would be OK to do one more release of Twisted and announce that as > the last release supporting Python 3.5, before > dropping support? Yeah; whenever we drop a Python version we should always support at least one more

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-15 Thread Craig Rodrigues
Personally, I don't have any dependencies on Python 3.5. I just suggested once year's notice to give people time to adjust, but if no one really cares, dropping 3.5 support some time this year is fine by me. Maybe it would be OK to do one more release of Twisted and announce that as the last

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-15 Thread Craig Rodrigues
On Wed, May 13, 2020 at 10:05 PM Amber Brown (hawkowl) < hawk...@atleastfornow.net> wrote: > > So, I guess if we have 3.8 support, the next release can announce the > dropping of 3.5, and then the release after that can be the final one > with support. > In trunk, on Python 3.8, all the tests in

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-14 Thread Glyph
> On May 14, 2020, at 3:55 AM, Amber Brown wrote: > > > > On Thu, 14 May 2020, at 16:54, Glyph wrote: >> >>> $ /usr/bin/python3 >>> Python 3.7.3 (default, Apr 7 2020, 14:06:47) >>> [Clang 11.0.3 (clang-1103.0.32.59)] on darwin >>> Type "help", "copyright", "credits" or "license" for more

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-14 Thread Amber Brown
On Thu, 14 May 2020, at 16:54, Glyph wrote: > > > $ /usr/bin/python3 > > Python 3.7.3 (default, Apr 7 2020, 14:06:47) > > [Clang 11.0.3 (clang-1103.0.32.59)] on darwin > > Type "help", "copyright", "credits" or "license" for more information. > > >>> import sys > > >>> sys.executable > >

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-14 Thread Glyph
> On May 13, 2020, at 11:13 PM, Amber Brown wrote: > > On Thu, 14 May 2020, at 16:09, Hynek Schlawack wrote: >> >> >>> On 14. May 2020, at 07:04, Amber Brown (hawkowl) >>> wrote: >>> >>> - MacOS doesn't ship a Python 3, but homebrew/python.org offer 3.8 easily. >> >> FWIW this is not true

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-14 Thread Amber Brown
On Thu, 14 May 2020, at 16:09, Hynek Schlawack wrote: > > > > On 14. May 2020, at 07:04, Amber Brown (hawkowl) > > wrote: > > > > - MacOS doesn't ship a Python 3, but homebrew/python.org offer 3.8 easily. > > FWIW this is not true anymore. Catalina comes – for all its faults – > with

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-14 Thread Hynek Schlawack
> On 14. May 2020, at 07:04, Amber Brown (hawkowl) > wrote: > > - MacOS doesn't ship a Python 3, but homebrew/python.org offer 3.8 easily. FWIW this is not true anymore. Catalina comes – for all its faults – with Python 3.7: ❯ /usr/bin/python2 WARNING: Python 2.7 is not recommended. This

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-13 Thread Amber Brown
On Thu, 14 May 2020, at 15:13, Glyph wrote: > On May 13, 2020, at 10:04 PM, Amber Brown (hawkowl) > wrote: > > > > On 14/5/20 5:10 am, Craig Rodrigues wrote: > >> I would like to propose that Twisted drop support for Python 3.5 one year > >> from now in 2021. > > > > I was considering

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-13 Thread Amber Brown
Xenial's 3.5.1/3.5.2 sucks and doesn't have some asyncio functionality (due to it being provisional then?) which means things like Eliot doesn't work due to aiocontextvars barfing on missing functionality. There's also 20.04 LTS now, making 16.04 old-old-LTS. I don't think it's worth it. -

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-13 Thread Moshe Zadka
May 2021 seems to be right around when Xenial (Which has 3.5) falls into ESM, so maybe we can wait? I don't have strong feelings, but it is a datapoint. Moshe Z. On Wed, May 13, 2020, at 22:13, Glyph wrote: > On May 13, 2020, at 10:04 PM, Amber Brown (hawkowl) > wrote: > > > > On 14/5/20

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-13 Thread Glyph
On May 13, 2020, at 10:04 PM, Amber Brown (hawkowl) wrote: > > On 14/5/20 5:10 am, Craig Rodrigues wrote: >> I would like to propose that Twisted drop support for Python 3.5 one year >> from now in 2021. > > I was considering proposing dropping it soon (I was thinking when we had 3.8 >

Re: [Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-13 Thread Amber Brown (hawkowl)
I was considering proposing dropping it soon (I was thinking when we had 3.8 support, that 3.6/3.7/3.8 is a reasonable compatibility matrix). Why I think this is probably fine: - Debian Stable (buster) has 3.7. oldstable (stretch) has 3.5.3, but I don't think we care about oldstable. - Ubuntu

[Twisted-Python] [RFC] Drop support for Python 3.5 sometime after May 2021?

2020-05-13 Thread Craig Rodrigues
I would like to propose that Twisted drop support for Python 3.5 one year from now in 2021. Reasons: 1. Python 3.5.9 will be the final release of Python 3.5, in November 2019 ( https://www.python.org/dev/peps/pep-0478/ ) 2. Python 3.6.0 was released in December 2016 (