Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #14782
| From | Graham Inggs <ginggs@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python, linux.debian.devel.release |
| Subject | Re: Python 3.11 for bookworm? |
| Date | 2022-12-26 21:50 +0100 |
| Message-ID | <FH2A1-dryc-1@gated-at.bofh.it> (permalink) |
| References | <FFc0N-cezl-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
Hi Matthias On Wed, 21 Dec 2022 at 18:24, Matthias Klose <doko@ubuntu.com> wrote: > while we have not an 100% agreement to go ahead, I think we should aim for 3.11. Action speaks louder than words, and there's been a whole lot of work done to push this forward. > The following steps would be: > > - accept the current python3-defaults into > testing (adding 3.11 as supported) This has been done. > - ask for a transition slot to upload (see #1026825) > python3-defaults with 3.11 as the default We're currently waiting on the PHP 8.2 (#1014460) and qtbase-opensource-src (#1025863) transitions. Although, there's been no progress on PHP 8.2, so this may be reconsidered. qtbase-opensource-src is currently blocked on a pyqt5 FTBFS on mipsel (#1026980), but there is a possible workaround. We hope to be able to start with the remaining steps soon. > - start the no-change NMUs > - file bug reports. > - fix issues > - let 3.11 as default migrate to testing. > If things don't go as planned, we could default back to 3.10. Mostly that would > be no-change uploads, however in the case of a 3.11 specific fix that doesn't > work for 3.10, these fixes would need reverting. I have no idea who many of > these we will introduce with this transition. OK, good to know we can still back out if we have to. > Also we might want to ask for some freeze exceptions for third party libraries, > that we can't fix before the feature freeze, unfortunately at this point we > cannot say which and how many packages would be affected. The release team is prepared to consider these on a case-by-case basis. Regards Graham
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: Python 3.11 for bookworm? Matthias Klose <doko@ubuntu.com> - 2022-12-21 19:30 +0100
Re: Python 3.11 for bookworm? Sandro Tosi <morph@debian.org> - 2022-12-22 01:20 +0100
Re: Python 3.11 for bookworm? Nicholas D Steeves <sten@debian.org> - 2022-12-22 02:30 +0100
Re: Python 3.11 for bookworm? "M. Zhou" <lumin@debian.org> - 2022-12-22 06:10 +0100
Re: Python 3.11 for bookworm? Thomas Goirand <zigo@debian.org> - 2022-12-28 02:00 +0100
Re: Python 3.11 for bookworm? Andreas Tille <andreas@an3as.eu> - 2022-12-30 10:30 +0100
Re: Python 3.11 for bookworm? Thomas Goirand <zigo@debian.org> - 2023-01-05 14:00 +0100
Re: Python 3.11 for bookworm? Andreas Tille <andreas@an3as.eu> - 2023-01-07 09:10 +0100
Re: Python 3.11 for bookworm? Andrius Merkys <merkys@debian.org> - 2023-01-07 09:30 +0100
Re: Python 3.11 for bookworm? Andrius Merkys <merkys@debian.org> - 2023-01-09 16:50 +0100
Re: Python 3.11 for bookworm? Andreas Tille <andreas@an3as.eu> - 2023-01-16 17:30 +0100
Re: Python 3.11 for bookworm? Thomas Goirand <zigo@debian.org> - 2023-01-17 01:10 +0100
Re: Python 3.11 for bookworm? Andreas Tille <tille@debian.org> - 2023-01-17 07:50 +0100
Re: Python 3.11 for bookworm? Étienne Mollier <emollier@emlwks999.eu> - 2023-01-10 22:50 +0100
Re: Python 3.11 for bookworm? Stefano Rivera <stefanor@debian.org> - 2022-12-22 13:50 +0100
Re: Python 3.11 for bookworm? Timo Röhling <roehling@debian.org> - 2022-12-22 14:00 +0100
Re: Python 3.11 for bookworm? Stefano Rivera <stefanor@debian.org> - 2022-12-22 19:50 +0100
Re: Python 3.11 for bookworm? "M. Zhou" <lumin@debian.org> - 2022-12-23 00:30 +0100
Re: Python 3.11 for bookworm? "M. Zhou" <lumin@debian.org> - 2022-12-23 00:40 +0100
Re: Python 3.11 for bookworm? Graham Inggs <ginggs@debian.org> - 2022-12-26 21:30 +0100
Re: Python 3.11 for bookworm? Graham Inggs <ginggs@debian.org> - 2022-12-26 21:50 +0100
csiph-web