Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: c.buhtz@posteo.jp Newsgroups: linux.debian.maint.python Subject: Re: Python 3.13 addition as a supported Python version started Date: Wed, 13 Nov 2024 11:50:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Nov 13 10:45:04 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-9.496 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Mailing-List: archive/latest/22526 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/e6105a560b067c47ecc754a0ce40ed8c@posteo.de Approved: robomod@news.nic.it Lines: 39 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Wed, 13 Nov 2024 10:43:55 +0000 X-Original-Message-ID: X-Original-References: <2431386e-e5e5-4041-ad7d-0b6ea31b585e@debian.org> <648982297.8392310.1731492266966.JavaMail.zimbra@synchrotron-soleil.fr> Xref: csiph.com linux.debian.maint.python:16451 Hello, I am an upstream maintainer and ask just because I want to learn. It was a similar case before the Debian 12 release introducing Python=20 3.12 near to the freeze. Why are fresh Python releases introduced so=20 early and near to the next Debian release? This is not how I do experience Debian at all. This is not "rock solid".=20 Python 3.13 is very fresh, no one needs it yet. I see no problem=20 introducing it with Debian 14 in 2027. For my project it does not matter directly. I do support 3.13. But this=20 process does bind a lot of resources on Debian which could be used more=20 productive into other problems. Who decide which Python version is introduced in Debian? Isn't there a=20 council for heavy decisions like this? Regards, Christian Buhtz Am 13.11.2024 11:04 schrieb PICCA Frederic-Emmanuel: > do we know how long we will have to fix all the FTBFS and autopkgtest > before the freeze ? >=20 > I am a bit worrying for the scientific stack , will we have enough > time to work with our upstream in order to fix all these FTBFS. In the > scientific stack, things are going slowly.... >=20 > We are not 100% of our time dedicated to Debian work... so I hope that > it will not ruine the effort of the trixie cycle for scientific > softwares. >=20 > moving to Python 3.12 was not that simple... >=20 > Cheers >=20 > Fr=C3=A9d=C3=A9ric