Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #16675 > unrolled thread
| Started by | Julian Gilbey <julian@d-and-j.net> |
|---|---|
| First post | 2025-01-10 15:10 +0100 |
| Last post | 2025-01-12 09:20 +0100 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.maint.python
New python3-defaults uploaded making Python 3.13 default Julian Gilbey <julian@d-and-j.net> - 2025-01-10 15:10 +0100
Re: New python3-defaults uploaded making Python 3.13 default Andrey Rakhmatullin <wrar@debian.org> - 2025-01-10 15:50 +0100
Re: New python3-defaults uploaded making Python 3.13 default Julian Gilbey <julian@d-and-j.net> - 2025-01-12 09:20 +0100
| From | Julian Gilbey <julian@d-and-j.net> |
|---|---|
| Date | 2025-01-10 15:10 +0100 |
| Subject | New python3-defaults uploaded making Python 3.13 default |
| Message-ID | <K3nS2-7Bd5-1@gated-at.bofh.it> |
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
[toc] | [next] | [standalone]
| From | Andrey Rakhmatullin <wrar@debian.org> |
|---|---|
| Date | 2025-01-10 15:50 +0100 |
| Message-ID | <K3ouK-7Cnn-9@gated-at.bofh.it> |
| In reply to | #16675 |
[Multipart message — attachments visible in raw view] — view raw
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
[toc] | [prev] | [next] | [standalone]
| From | Julian Gilbey <julian@d-and-j.net> |
|---|---|
| Date | 2025-01-12 09:20 +0100 |
| Message-ID | <K41mp-89pO-1@gated-at.bofh.it> |
| In reply to | #16676 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web