1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.PYTHON

  • New python3-defaults uploaded making Python 3.13 default

    From Julian Gilbey@21:1/5 to All on Fri Jan 10 15:10:02 2025
    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.

    Best wishes,

    Julian

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rakhmatullin@21:1/5 to Julian Gilbey on Fri Jan 10 15:50:02 2025
    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.


    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmeBMUMtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh 1iAQAI9UgAnkAU73qT2ti3Q2CmZH09/X4b/Rj47qoF4CGGvtdqqh6SdOlTCptPDq AINbcCACeG/m6O96KLGsE4j7+uBmEII7vJmaCvmuH/9uRwPLgpkxbPpT+9ktyZiA MgIZP93rHpKNwiIVtsI+jaflslaIyWNhwae1dKlWrg6y7jbalo0ExDR52ut5+hvr xUnyAgLDswO7VzsgiLqFMxKFOf5IoxL8M0VlJkI16VjCubzYrJ2h6RpLeFJkyGVa q4cDHkKSoBbZn/jQJ2jzPtMAco3WCsbrMmREJXUKt/4lruVhjffZvxnc3AP3ACnw z83u46GsgyFV5aUnkjXgCsHjbIz2/xKWuasiNNH081NMLNZCl4lECfSgo+dpWsP9 M861ZFdcvgH0zac4NIN0Y84xOp3GdDKAi2n8Cf5nr2l4NQcOqiDYRu571xW47ucq pO0uCglki7OnnOhAQTPcgOf7uvJuiBw2m8k2+w3dtT7khQJ3G5aQ73hoNzTbZCD+ zdF2G2gjy9za76E9qxxXQ6SU4klql1HMIW5ag3EVlXNHMH4BpEnLabZYw3jyf8bu FAEAsNhzmAWdu78N5+3BJ/GxmypYNMdwq/gIoBwvhFeg/L3sqG2BMkidLBgOdi9n 4pL+HohCvjvUfr18blJbiNLI3WA/fPRkkpzzQ8rNMZ1Iahnv
    =juHt
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Julian Gilbey@21:1/5 to Andrey Rakhmatullin on Sun Jan 12 09:20:01 2025
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)