Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #15302 > unrolled thread

Preparing for Python 3.12

Back to article view | Back to linux.debian.maint.python

Contents

  Preparing for Python 3.12 Matthias Klose <doko@debian.org> - 2023-11-07 11:50 +0100
    Re: Preparing for Python 3.12 Matthias Klose <doko@debian.org> - 2023-11-07 15:20 +0100
    Re: Preparing for Python 3.12 Matthias Klose <doko@debian.org> - 2023-12-03 15:10 +0100
      Re: Preparing for Python 3.12 Stefano Rivera <stefanor@debian.org> - 2023-12-06 22:10 +0100

#15302 — Preparing for Python 3.12

Python 3.12 was released a month ago, and it's time to prepare for the 
update in unstable, first adding 3.12 as a supported version.


There s a tracker for adding 3.12 as a supported version [1], also there 
are the first bug reports filed for issues related to 3.12 [2].


As usual, it's difficult to find about issues in higher stages before 
building packages in lower/earlier stages of the transition.  Therefore 
we started again adding 3.12 in Ubuntu, and then filing and fixing 
issues in unstable before adding 3.12 in Debian unstable.


This Ubuntu tracker can be seen at [3]. Note that i386 is only a partial 
architecture, and that Ubuntu doesn't run the tests on riscv64 during 
the build (so packages succeeding to build on riscv64 but not on the 
other architectures most likely show test failures instead of build 
failures).


Ubuntu's update_excuses for python3-defaults also shows autopkg tests 
failing with 3.12 supported, although this information is a bit out of 
date, due to infrastructure issues for the autopkg testers.


The plan is to make 3.12 supported in unstable at the end of November, 
or earlier if possible, so that other transitions aren't blocked by the 
addition of 3.12. Then planning for the defaults change in January.  
While this timeline is not that much needed for 3.12, it will be a good 
exercise for 3.13, so that we get 3.13 as the default into the trixie 
release.


Matthias


[1] https://bugs.debian.org/1055085

[2] 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=python3.12;users=debian-python@lists.debian.org

[3] 
https://ubuntu-archive-team.ubuntu.com/transitions/html/python3.12-add-v2.html

[4] 
https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html#python3-defaults

[toc] | [next] | [standalone]

#15303

On 07.11.23 14:06, Thomas Goirand wrote:
> When 3.12 because an available version, it would help a lot to have 
> someone like Lucas Nusbaumm to rebuild all reverse dependencies of 
> Python. Is that something planned?

No.  A test rebuild with a stack of 12 dependency levels doesn't make 
much sense.  You'll only get reasonable results for the first dependency 
level, not the other 11 levels.

What we've done until now was to test the addition of 3.12 in a PPA, 
making sure that we can build up the dependency up to key packages like 
cython, numpy, test frameworks and others.  After that, doing the work 
in the archive in a way that hopefully doesn't block other transitions 
too much.

Also doing the whole work in a PPA or shadow archive is problematic, as 
you have to make sure that the PPA / shadow archive doesn't get out of 
sync with the normal archive.  A challenge over time with 1000+ packages.

I'm planning to ask Lucas for a normal test rebuild of unstable, once we 
have a reasonable amount of packages built with 3.12 in unstable.  Bugs 
for these will be filed, but we probably have to usertag these our self.

Matthias

[toc] | [prev] | [next] | [standalone]

#15324

python3-defaults, adding Python 3.12 as a supported version, is now in 
unstable.  We don't expect to block other transitions while working on 
the first step of getting to 3.12.

We probably will see some Python related build failures while binNMUing 
around 600 packages to add 3.12 as a supported version.  If you see 
builds failing because of a missing 3.12 extension, please just wait a 
few days until all the binNMUs are done.

For the progress, see (ignoring the 'unknown' status)
https://release.debian.org/transitions/html/python3.12-add.html

Matthias


On 07.11.23 11:27, Matthias Klose wrote:
> Python 3.12 was released a month ago, and it's time to prepare for the 
> update in unstable, first adding 3.12 as a supported version.
> 
> 
> There s a tracker for adding 3.12 as a supported version [1], also there 
> are the first bug reports filed for issues related to 3.12 [2].
> 
> 
> As usual, it's difficult to find about issues in higher stages before 
> building packages in lower/earlier stages of the transition.  Therefore 
> we started again adding 3.12 in Ubuntu, and then filing and fixing 
> issues in unstable before adding 3.12 in Debian unstable.
> 
> 
> This Ubuntu tracker can be seen at [3]. Note that i386 is only a partial 
> architecture, and that Ubuntu doesn't run the tests on riscv64 during 
> the build (so packages succeeding to build on riscv64 but not on the 
> other architectures most likely show test failures instead of build 
> failures).
> 
> 
> Ubuntu's update_excuses for python3-defaults also shows autopkg tests 
> failing with 3.12 supported, although this information is a bit out of 
> date, due to infrastructure issues for the autopkg testers.
> 
> 
> The plan is to make 3.12 supported in unstable at the end of November, 
> or earlier if possible, so that other transitions aren't blocked by the 
> addition of 3.12. Then planning for the defaults change in January. 
> While this timeline is not that much needed for 3.12, it will be a good 
> exercise for 3.13, so that we get 3.13 as the default into the trixie 
> release.
> 
> 
> Matthias
> 
> 
> [1] https://bugs.debian.org/1055085
> 
> [2] 
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=python3.12;users=debian-python@lists.debian.org
> 
> [3] 
> https://ubuntu-archive-team.ubuntu.com/transitions/html/python3.12-add-v2.html
> 
> [4] 
> https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html#python3-defaults
> 
> 

[toc] | [prev] | [next] | [standalone]

#15331

Hi Matthias (2023.12.03_14:03:44_+0000)
> We probably will see some Python related build failures while binNMUing
> around 600 packages to add 3.12 as a supported version.  If you see builds
> failing because of a missing 3.12 extension, please just wait a few days
> until all the binNMUs are done.
> 
> For the progress, see (ignoring the 'unknown' status)
> https://release.debian.org/transitions/html/python3.12-add.html

This is a great time for new Python Team contributors to get involved in
helping to support Python 3.12. This is a time when upstream Python
knowledge can be more helpful than Debian packaging experience.

Look go down the list of packages and investigate the ones with a red
line.  Either they have failed to build (top of the list) or they
haven't been built against 3.12 yet (bottom of the list).

As we investigate these, we'll file FTBFS bugs against them (which
usually show up on buildd.debian.org, below the builds).

Usually the process is:
1. Read the bug to see the investigation so far.
2. Check the upstream bugtracker for related bugs.
3. See if there is a new upstream release or commit that promises to
   support Python 3.12 (or whatever the issue is).
4. Report back on the bug
5. Prepare an upload.

We're mostly coordinating in #debian-python on IRC.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web