Guido van Rossum

Maybe they're using...

functions that are defined by the Python 3 runtime that won't be in the Python 4 runtime, those functions will not work.

They'll have to find an alternative

But they can experiment with that and sort of write test applications.

And that would be a way to transition.

And that could be a series of releases where the Python 4 is more and more imminent.

We have supported more and more third-party extension modules to have solid support that works for NoGil Python for that new API application.

And then sort of Python 4.0 is like the official moment that the mayor comes out and cuts the ribbon.

And now the sort of no-guilt mode is the default and maybe the only mode there is.

Oh my, that

I should really have a standard answer for that question, but like a positive standard answer.

But my current standard answer is that I'm not a big user of third-party packages.

When I write Python code, I'm usually developing some tooling around building Python itself.

And the last thing we want is dependencies on third-party packages.

So I tend to just use the standard library.

That's where your focus is.

Well, usually when something's missing from the Standard Library, nowadays...

It is a relatively new idea, and there is a third-party implementation or maybe possibly multiple third-party implementations, but they evolve at a much higher rate than they could when they're in the standard library.

So it would be a big reduction in activity to...

incorporate things like that in the standard library.