Re: python 3.7 removal proposal (before upstream EOL!!)

[nia <nia%NetBSD.org@localhost>]

On Sun, Oct 30, 2022 at 07:51:49PM -0400, Greg Troxel wrote:
> The point is that the breakage is showing up and not getting fixed, so
> it is de facto too hard, relative to the effort that is being applied.
> We need a get-well plan from that.

Speaking from the perspective of having just done a lot of work to
keep py-cryptography working on our NetBSD ports that don't support
rust, I think it's not very nice that people can commit updates that
cause such widespread breakage and not do anything to fix them,
without them being reverted.

In particular, I had to email some of the people that build NetBSD
binary packages and ask them to do something other than run package
builds for this quarter, because the fixes are very intrusive,
difficult to pull up, and I didn't realize how serious the breakage
was until too late. So we have to wait until Q4 for reliable builds
again.

Many users don't have the time to constantly watch the pkgsrc tree
for something they rely on being pulled from under their feet by
surprise.