>>> 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.

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

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.

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.

those are two uppercase i.

Damned IIm

keming crimes ?

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?"

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.

Is that the recent layoffs? did I miss some things ?

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.

I'm guessing you could also ask @jupyter.org, but i'm not sure it is monitored, nor who controls it...

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

We have a website version of the Project 2025 tracker now

(Big thanks to u/mollynaquafina)

project2025-tracker.vercel.app

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.

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 ?