Hi all,
On 11/11/26 01:08, Sharlatan Hellseher wrote:
Hi,
Python team is not expecting any changes with large rebuilds.
I try to build python manifest locally to spot any urgent failures
after mesa-update.
ghc takes hours to build which depends on Python
Rust dependency on Python and
Java depends on Python as well
Each bootstrap step takes up to 40min on 16x threads
To be clear: python-team only updates the minor version of Python, and
we already verified before the mesa-update that these chains all build.
So python-team should be ready.
(It also updates some packages, but does not switch to e.g. Python 3.13
is what I mean.)
Nevertheless, I personally am fine with both merging and not merging.
There are security fixes on Python team, but there will be more security
issues after the release, so I think it's a fools errant to try to get
them all in now.
In other email thread discussing power usage and rebuild reputation
It was higlited that packages collection is more Graph problem
rather than catalogue by team responsibilities one.
We will probably need a slow-moving `python-for-building-toolchains` or
whatever soon, because some of those build trains need Python <= 3.12,
for example LLVM 13.
There should be no problem to use Python 3.12 to build Rust, and then
use Rust to build Python 3.14 packages. This would simplify our
dependency graph significantly.
Hugo