Pablo Galindo

changing and adapting your code and all the libraries for a two-year worth of changes is brutal. Which means that, and we saw that before, right? Which means that until new libraries are compatible with the new version, there's a non-trivial amount of time.

changing and adapting your code and all the libraries for a two-year worth of changes is brutal. Which means that, and we saw that before, right? Which means that until new libraries are compatible with the new version, there's a non-trivial amount of time.

So as a user or as a company employee that you want to leverage these new features, you probably want to wait a lot because now people talk about scheduling the work and finding even how much it is. And library maintainers say, well, I will fix it later. But when the changes are smaller,

So as a user or as a company employee that you want to leverage these new features, you probably want to wait a lot because now people talk about scheduling the work and finding even how much it is. And library maintainers say, well, I will fix it later. But when the changes are smaller,

that is like, psychologically speaking, obviously, in reality is more or less the same, modulus and nonlinear interaction. But in general, when the changes are smaller, then it's more enticing because at least you know, okay, maybe this, this, this, and this thing. And sure, maybe you need to wait for another library to do it, but like,

that is like, psychologically speaking, obviously, in reality is more or less the same, modulus and nonlinear interaction. But in general, when the changes are smaller, then it's more enticing because at least you know, okay, maybe this, this, this, and this thing. And sure, maybe you need to wait for another library to do it, but like,

Normally, like right now, what we have seen compared with 3.8 when we started doing this, right, is that people jump earlier. Like before, for instance, one of the biggest libraries is NumPy, which is numerical computing in C and Fortran and whatnot. So that library used to take a long time to be compatible with new versions, like months or sometimes even like half a year or something.

Normally, like right now, what we have seen compared with 3.8 when we started doing this, right, is that people jump earlier. Like before, for instance, one of the biggest libraries is NumPy, which is numerical computing in C and Fortran and whatnot. So that library used to take a long time to be compatible with new versions, like months or sometimes even like half a year or something.

And right now we are having it almost day one. So this is fantastic because people that want to use the new features in the language, they are not held back by the fact that their own particular dependencies don't have the support for this.

And right now we are having it almost day one. So this is fantastic because people that want to use the new features in the language, they are not held back by the fact that their own particular dependencies don't have the support for this.

Most of these things, I don't think you can approach it from a data-driven kind of, like, perspective because it's very difficult to say what is better, what is worse. But, like, certainly, like, you know, from a psychological point of view, I think it's, again, I think you have a very good point. Like, not too soon, like, not too often, sorry, but, like, also not too, like, lagging behind.

Most of these things, I don't think you can approach it from a data-driven kind of, like, perspective because it's very difficult to say what is better, what is worse. But, like, certainly, like, you know, from a psychological point of view, I think it's, again, I think you have a very good point. Like, not too soon, like, not too often, sorry, but, like, also not too, like, lagging behind.

I think it's, earlier is better, maybe not too early, like, every three weeks it will be impossible for a compiled language, like, We will ship a JIT compiler that unoptimizes your code, right? It will be like 6% or something. But one year, yeah, good.

I think it's, earlier is better, maybe not too early, like, every three weeks it will be impossible for a compiled language, like, We will ship a JIT compiler that unoptimizes your code, right? It will be like 6% or something. But one year, yeah, good.

I think everyone, a non-trivial amount of listeners probably are saying, what is that wheel? What is this thing?

I think everyone, a non-trivial amount of listeners probably are saying, what is that wheel? What is this thing?

Is this another word for a build? It's like a build? Basically, it's a binary package. So it's a package that doesn't contain Python code only.

Is this another word for a build? It's like a build? Basically, it's a binary package. So it's a package that doesn't contain Python code only.

Well, this is the key, right? Because the Python package index used to, well, I think it still is, it's called a cheese shop because it's all about these Monty Python references and jokes, right? So it's a sketch of Monty Python that goes to this cheese shop. And a wheel is a wheel of cheese.

Well, this is the key, right? Because the Python package index used to, well, I think it still is, it's called a cheese shop because it's all about these Monty Python references and jokes, right? So it's a sketch of Monty Python that goes to this cheese shop. And a wheel is a wheel of cheese.