Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Julian Gilbey Newsgroups: linux.debian.maint.python Subject: Re: New python3-defaults uploaded making Python 3.13 default Date: Sun, 12 Jan 2025 09:20:01 +0100 Message-ID: References: X-Original-To: Andrey Rakhmatullin X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Jan 12 08:15:31 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.198 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_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -4.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailing-List: archive/latest/22774 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/Z4N6EXzkF1mxYUCC@d-and-j.net Approved: robomod@news.nic.it Lines: 30 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Sun, 12 Jan 2025 08:15:13 +0000 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.python:16679 On Fri, Jan 10, 2025 at 07:40:08PM +0500, Andrey Rakhmatullin wrote: > On Fri, Jan 10, 2025 at 02:05:06PM +0000, Julian Gilbey wrote: > > Hi all, > > > > Just to let you know that Matthias and Stefano upload python3-defaults > > 3.13.1 to unstable earlier this week, making Python 3.13 the default. > > I just got a FTBFS bug report which turned out to be because the build > > used python3 to perform an action, and python3.12 succeeds on this but > > python3.13 fails. It took me a while to discover the cause, so just > > wanted to share this information to save other people time if they > > receive similar FTBFS reports. > > Yup. You can watch the progress on > https://release.debian.org/transitions/html/python3.13-default.html and it > looks less problematic than the 3.13-add transition but still has quite a > lot of new blocking bugs. Thanks Andrey! My package (jupyter-client) isn't listed there, as the (binary) dependency is on python3:any. But the build turns out to succeed when python3 -> python3.12 but fail when python3 -> python3.13 - it's sphinx-build that fails. I still haven't solved the bug, but at least I know which change has caused the breakage. Best wishes, Julian