Re: python 3.7 problems

[Adam <adam%netbsd.org@localhost>]

> So a recent update of py-setuptools_scm introduced a cyclic dependency
> for python 3.7 because it needs the importlib-metadata module, but
> that needs py-setuptools_scm to build.
> 
> The missing dependency now leads to heavy fallout for python 3.7 modules, a sample:
> 
> http://www.ki.nu/pkgsrc/reports/current/NetBSD-9.0/20221023.0731/py37-py-1.11.0/build.log
> http://www.ki.nu/pkgsrc/reports/current/NetBSD-9.0/20221023.0731/py37-iniconfig-1.1.1nb1/build.log
> http://www.ki.nu/pkgsrc/reports/current/NetBSD-9.0/20221023.0731/py37-dateutil-2.8.2nb1/build.log
> http://www.ki.nu/pkgsrc/reports/current/NetBSD-9.0/20221023.0731/py37-filelock-3.8.0/build.log
> http://www.ki.nu/pkgsrc/reports/current/NetBSD-9.0/20221023.0731/py37-importlib-resources-3.0.0nb2/build.log
> http://www.ki.nu/pkgsrc/reports/current/NetBSD-9.0/20221023.0731/py37-lazy-object-proxy-1.7.1nb1/build.log
> http://www.ki.nu/pkgsrc/reports/current/NetBSD-9.0/20221023.0731/py37-execnet-1.9.0nb1/build.log
> 
> Is someone willing to fight the windmills and get one of the upstreams
> to fix the cycle?
> 
> Or should we just give up on python 3.7? The official EOL is
> 2023-06-27 but we already have some packages in pkgsrc that do not
> support this version any longer.
> 
> Other suggestions?
> Thomas

Now that Python 3.11 is out, I would like to remove Python 3.7 as it causes too much trouble already.
Five Python versions in PkgSrc is enough.

Adam