Re: python 3.9 and 3.10?

[Greg Troxel <gdt%lexort.com@localhost>]

Thomas Klausner <wiz%gatalith.at@localhost> writes:

> On Sat, Jul 05, 2025 at 08:57:21AM -0400, Greg Troxel wrote:
>> It seems that the python world has decided that 3.11 is the new minimum
>> reasonable version.
>> 
>> Where are we on the process of dropping 3.9 and 3.10?   It seems we
>> should begin to think about it, at least.
>> 
>> If not dropping because of formal support, perhaps dropping from the
>> default build.
>
> We have already removed 39 from the versions for which we build module
> packages by default. I guess it's time to add 310 to that list.

I had forgotten about 39.  Yes, I think it's time to drop 310 from
build-modules-by-default.

> (upstream will support 3.9 until this fall, and 3.10 until fall 2026,
> but that doesn't help if the modules don't)

Upstream the python distribution, but as you say there is also upstream
the ensemble of important python packages.  It feels like the python
community has (just) decided that 3.10 is no longer ok to use, in that
packages feel free to release versions without 3.10 support.


Overall, I don't know if people are using old python from pkgsrc much,
and given the amount of work it takes to cope, I would choose to steer
to follow community deprecation faster and drop from default build as
soon as it becomes painful.

Either that or someone(tm) can implement cascading limited-version
support, so that building py-foo not marked excluding 310 will
cleanly/simply fail (without upsetting people that run pbulk and view it
as Really Serious to have "tree is broken") if it depends on py-bar that
excludes 310.