On 9/6/26 10:17, Maximiliano Curia wrote:
Just some context, during the Python BoF in DebConf one of the topics
was about Python 3.15, about to be released in October and aimed to be
included in forky, I've done some follow up in [1], and been working to
make all packages work with python 3.15.
thanks for doing that!
I've been ccing the list when sending a new bug submit as I considered
that these were of interest to the list, I'll stop adding the cc to the
list, the issues should still be visible in the bts by usertag or in the
tracker for the packages that have the team tracker as maintainer.
Could it be better for them to have a low priority bug associated that
could be
raised later on?
They are mostly normal bugs for now, and they can be raised to serious
when python3-defaults in sid add python 3.15 as the supported version.
I would even raise the severity of these issues to important for now.
The release is about three weeks away, and the upload adding 3.15 as a
supported version is planned a month after the 3.15 upstream release,
when all these become RC. It's much better to fix the known issues now,
the less work we have in about tho months time.
Matthias
