Hi,
Seems like the process to update the default python is ongoing from what
I've seen in Bugzilla.
I know these bugs are important blockers right now (I can't give you
status since I just lurk):
1. 285957 – lang/python312 as default python
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285957>
* 277826 – [exp-run]science/py-scipy: Update to 1.17.0
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277826>
2. 284845 – textproc/py-sphinx: Update to 8.2.3
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284845> (blocks
python 13/14)
I am currently building on python 3.13 with no build errors (I had to
use the version sphinx patched to 9.1.0 attached in the ticket), and
have been running python 3.12 for a while now without issues. I haven't
started testing python 3.13 yet, so I may just skip to 3.14.
-Matthew
On 2/9/2026 4:45 PM, Dan Mahoney (ports) wrote:
On Feb 9, 2026, at 1:37 PM, Guido Falsi<[email protected]> wrote:
Hi,
I'll take the risk of prodding the wasp nest related to python version upgrade.
I'm forced to do this as the maintainer of deskutils/calibre.
Tat project has recently released a new major version with and hard requirement of python
3.14 or newer [1]. It uses new constructs and imports in multiple places, as much as
needed to make the "hack it to work with 3.11" strategy not viable (short of of
creating a full fork of the software).
So my question, which is not a demand, but just a request for information I did
not find elsewhere:
Is there any effort underway to update the python default to a newer version?
Also, apart from that, as I explain in [1], if I simply put USES=python:3.14+
in the Makefile, the port fails to build due to many of its requirements
failing to provide a py-314 flavor. Is there any work on this front?
I ask to know if there is some effort I can join and maybe help, although I'm
not a python expert.
Also, 3.11 currently shows in pkg audit (Hi, we operate critical internet infrastructure,
this affects us, we have auditors to answer who question our decisions to deploy software
with known CVE's), and the python project has not seen the urgency in releasing a
3.11.15, even though it's currently in a "security patches only" state -- um,
this would be that, please do the needful!
I've been in touch with the release maintainers there, but there's not a
perceived sense of urgency here, and of course, in BSD-land, everything's
nailed to 3.11.
If other people are in touch with the python folks, this would probably be a
good sentiment to echo.
Is there some way dayjob can help with this?
-Dan
