M B
mbussonn.bsky.social
M B
@mbussonn.bsky.social
Python Dev – If you know who I am, feel free to follow me – if not I'm probably not interesting, and a bit private.
>>> ast.Constant('a').n

DeprecationWarning: Attribute n is deprecated and will be removed in Python 3.14; use value instead.

Since when can I use `.value` ? Or should I have a conditional depending on version?

How long does it takes you, and multiply this by dozen of warnings.
December 11, 2025 at 6:32 PM
And it's a UI problem, because almost none of the libraries says since when replacement are available dev glance over DeprecationWarnings, thinking "I don't want to spend 1/2h diving into release notes of git blame". Example
What’s new in Python 3.14
Editors, Adam Turner and Hugo van Kemenade,. This article explains the new features in Python 3.14, compared to 3.13. Python 3.14 was released on 7 October 2025. For full details, see the changelog...
docs.python.org
December 11, 2025 at 6:32 PM
Well, but that's a generic comment for deprecation warnings. And I don't have the full APIs of all libraries when I fix things. X added; it's bad; add Y; deprecated X; "please use Y". I don't want to go spelunk to know since when I can use Y. "Use Y that was always available" is better.
December 11, 2025 at 6:32 PM
Suggestion: I see in the the PR you link to that it list when the removal will be; but I almost only care about since when the replacement is available. if > my_min_version, I can update my code; if not, I need a conditional When it will be removed is not useful for me except putting pressure.
December 10, 2025 at 9:20 PM
those are two uppercase i.
June 7, 2025 at 7:45 AM
Damned IIm
June 7, 2025 at 7:44 AM
keming crimes ?
June 6, 2025 at 1:06 PM
In a parallel world, "Python Community" is an "American Drama" on "LetFlix". ... "Last episode in python community: Pep 741 has been delayed due to Guido concern, Will the unexpected alliance of Brett and Carol be enough to convince the Former BDFL?"
May 23, 2025 at 6:33 AM
I guess drama might be a strong word. I always knew there were issues and disagreements, but I felt the community is always forging ahead in the same direction.
May 22, 2025 at 5:57 PM
Is that the recent layoffs? did I miss some things ?
May 22, 2025 at 10:07 AM
I'm also going to clarify that moving this is a _recognition_ of spyder maintainers work who have been doing most of the maintenance and features for years, that we 100% trust them, and want to give them more freedom to push it in the direction they wish.
May 11, 2025 at 4:09 PM
I'm guessing you could also ask @jupyter.org, but i'm not sure it is monitored, nor who controls it...
May 8, 2025 at 12:30 PM
No, but as far as I can tell nobody has the bandwidth to work on it. See github.com/jupyterlab/j... For why it's a lot more work than expected
Should we archive this project? · Issue #890 · jupyterlab/jupyterlab-desktop
Should we archive JupyterLab Desktop? Making regular new releases there is imperative from the security perspective (it is shipping a whole browser, with all its zero days), and it is also pretty h...
github.com
May 8, 2025 at 12:26 PM
Reposted by M B
We have a website version of the Project 2025 tracker now

(Big thanks to u/mollynaquafina)

project2025-tracker.vercel.app
Project 2025 Tracker
Track the progress on Project 2025
project2025-tracker.vercel.app
February 6, 2025 at 6:34 PM
Same for me, bluesky is limited, and I have other reasons not to come this year, but for the foreseeable future, US conferences/travel for me is a No. I know conference planning is a multi-year process though, ant that it can be out of your control.
April 30, 2025 at 10:36 AM
Unfortunately – I know you understand – currently, many cannot take the risk of travelling to the US for their safety, refuse to do so in solidarity. Hopping next year may be in a suitable country.

Is there by any chance a way to told the organisers: I would have come, but it's in the US ?
April 30, 2025 at 6:49 AM