tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re[2]: Python default -> 3.14?



Hi All,

I've follow the approach below after version change, was very smooth, so far for me looks good:

[NetBSD-drixter@devil:~]$ pkgin list | grep 314 | wc -l
      47
[NetBSD-drixter@devil:~]$ pkgin list | grep 313 | wc -l
       0
[NetBSD-drixter@devil:~]$


Quote from dholland which may help for some people like me once it will be implemented:
(of course we need to adjust the versions properly)
 
==cut==
My approach to this is:
- install python313
- explicitly build the minimum set of py313 modules that let you
build stuff (for 3.12 that apparently was:
py-flit_core
py-installer
py-pyparsing
py-packaging
py-pyproject_hooks
py-build
py-wheel
py-setuptools
)
- examine pkg_info -R python312 output for things that aren't
python modules and rebuild those
- examine the list of py312 modules for things I actually want (as
opposed to things installed because something else asked for
them) and build those for 3.13 (being careful not to waste time
rebuilding things that already got installed by something else)
- delete all python312 modules
- delete python312
 
It is a lot easier than updating everything after installing a new
release of the same Python, because you can safely just let the
depends do their thing.
 
==cut==

-- 
Marcin Gondek / Drixter
http://fido.e-utp.net/
AS56662


------ Original Message ------
From "Thomas Klausner" <wiz%netbsd.org@localhost>
To "Greg Troxel" <gdt%lexort.com@localhost>
Cc tech-pkg%netbsd.org@localhost
Date 31.10.2026 14:36:13
Subject Re: Python default -> 3.14?

On Wed, Oct 28, 2026 at 07:23:08AM +0100, Greg Troxel wrote:
Thomas Klausner <wiz%netbsd.org@localhost> writes:
 
> Python 3.14 has been in pkgsrc a long time, and the latest version is
> now 3.15.
>
> I propose that we change the default to 3.14 (currently, it is 3.13).
 
Looking at the python binary packages for NetBSD 11 amd64, the only
packages that exists for 3.13 but not 3.14:
 
py-backports.zstd: (included in 3.14+, so not a problem
 
py-torch: While this is important, the pkgsrc version is out of date.
It's 2.8.0 from August 2025, which isn't really that long ago, but
upstream has released 2.14.1 as a micro on the 7th minor release since
2.8.0! This is therefore not a reasont to refrain from updating to
3.14.
 
My take is that the small list of "3.13 packages exists but not 3.14"
means that changing to 3.14 is not only appropriate this minute, but is
likely overdue.
 
Thanks for the comparison.
 
I've just bumped the default version to 3.14.
 
I'd appreciate if it someone updated py-torch to a version supporting
newer Python versions.
Thomas


Home | Main Index | Thread Index | Old Index