On Feb 9, 2026, at 1:37rC>PM, Guido Falsi <mad@madpilot.net> wrote: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!
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.
On 09/02/2026 16:37, Guido Falsi wrote:
Hi,The other replies have covered the existing effort to get to 3.12 as default, which is a stopgap to 3.13. Generally python@'s procedure is to
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?
set the default to N-1, where N is the latest upstream CPython release branch.
Unlike previous default changes, 3.12 and later's changes have become
far more intrusive, specifically deprecations and removals of certain components that nearly every package has (historically) relied on. The greater Python package ecosystem has also not been the most timely to
act upon those changes let alone receive the information of them happening.
The main problem for us in ports is that setting a lower flavour bound
that is higher than the default is broken. This is because the flavour corresponding to the default will not exist, which causes poudriere-
bulk(8) to abort immediately. The workaround is to set the lower bound
to the current default, but set BROKEN on every flavour except for 3.14
(and soon 3.14t).
Also, apart from that, as I explain in [1], if I simply putWhich dependencies have an upper flavour bound to < 3.14?
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.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 59 |
| Nodes: | 6 (1 / 5) |
| Uptime: | 16:06:04 |
| Calls: | 810 |
| Calls today: | 1 |
| Files: | 1,287 |
| D/L today: |
10 files (21,017K bytes) |
| Messages: | 193,341 |