Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #14632
| From | Sandro Tosi <morph@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Python 3.11, bytecode and new internals |
| Date | 2022-11-21 18:40 +0100 |
| Message-ID | <FuiVX-5lkH-11@gated-at.bofh.it> (permalink) |
| References | <Fu9pD-5fnn-3@gated-at.bofh.it> <FuisV-5l9z-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Nov 21, 2022 at 12:03 PM Louis-Philippe Véronneau <pollo@debian.org> wrote: > > On 2022-11-21 02 h 08, Julian Gilbey wrote: > > I'm just flagging this up here, with a question about how we should > > proceed. Certainly we are not ready to make Python 3.11 the default > > Python version!! > > This is a concern I share and I think I've been pretty vocal about it. > > I feel the state of python packages for Bookworm with 3.10 was pretty > good and it seemed reasonable to prioritize stability for our next > stable release :) > > It's very frustrating to work on packaging python libraries and apps for > a whole release cycle, just to see all that work put in the bin at the > last minute because upstream doesn't support 3.11... this, 100 times > I've been told the current 3.11 transition was a test, and if it was > clear too many important things were broken and couldn't be fixed, we > would roll back and release using 3.10. why are we running a "test" this close to the release? *who* are we running this test for? who made this decision (i figure RT gave the go ahead, but still)? is there any searchable source for this claim? Thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Python 3.11, bytecode and new internals Julian Gilbey <julian@d-and-j.net> - 2022-11-21 08:30 +0100
Re: Python 3.11, bytecode and new internals Louis-Philippe Véronneau <pollo@debian.org> - 2022-11-21 18:10 +0100
Re: Python 3.11, bytecode and new internals Scott Kitterman <debian@kitterman.com> - 2022-11-21 18:30 +0100
Re: Python 3.11, bytecode and new internals Scott Kitterman <debian@kitterman.com> - 2022-11-22 15:20 +0100
Re: Python 3.11, bytecode and new internals Sandro Tosi <morph@debian.org> - 2022-11-21 18:40 +0100
Re: Python 3.11, bytecode and new internals Thomas Goirand <zigo@debian.org> - 2022-11-22 09:30 +0100
Re: Python 3.11, bytecode and new internals Julian Gilbey <julian@d-and-j.net> - 2022-11-22 11:00 +0100
Re: Python 3.11, bytecode and new internals Thomas Goirand <zigo@debian.org> - 2022-11-22 17:10 +0100
Re: Python 3.11, bytecode and new internals Julian Gilbey <julian@d-and-j.net> - 2022-11-22 18:00 +0100
Re: Python 3.11, bytecode and new internals Thomas Goirand <zigo@debian.org> - 2022-11-23 00:30 +0100
Re: Python 3.11, bytecode and new internals Julian Gilbey <julian@d-and-j.net> - 2022-11-23 08:40 +0100
csiph-web