Menu
Sign In Search Podcasts Charts People & Topics Add Podcast API Pricing

Pablo Galindo

👤 Person
238 total appearances

Appearances Over Time

Podcast Appearances

People actually now have like, you know, dates and they can, you know, put their lives around.

People actually now have like, you know, dates and they can, you know, put their lives around.

one of the the interesting you know side effects of this is that now people have this this impression that python is releasing too often so every single year is a new version and then the old version is like you know um out of uh support or like first back fix support and then security support so they have this feeling that you know they're going to be uh if they don't move fast enough uh they are going to be able to support super soon which which was always true is that

one of the the interesting you know side effects of this is that now people have this this impression that python is releasing too often so every single year is a new version and then the old version is like you know um out of uh support or like first back fix support and then security support so they have this feeling that you know they're going to be uh if they don't move fast enough uh they are going to be able to support super soon which which was always true is that

you get the numbers changing slower. So the impression was that it's happening slower. But right now, this is moving this impression that Python is changing too quickly, right? Or whatever it is.

you get the numbers changing slower. So the impression was that it's happening slower. But right now, this is moving this impression that Python is changing too quickly, right? Or whatever it is.

The other downside that this has is that, as you can see, for instance, for Python 3.13, it means that because we need to release every single year, we're releasing these features, maybe like big ones, like the Nogil or the JIT in particular, not being super exciting. So for instance, JIT in particular is 0% faster. Well, it's kind of cool, but why would you use it?

The other downside that this has is that, as you can see, for instance, for Python 3.13, it means that because we need to release every single year, we're releasing these features, maybe like big ones, like the Nogil or the JIT in particular, not being super exciting. So for instance, JIT in particular is 0% faster. Well, it's kind of cool, but why would you use it?

If we had a two-year release, maybe it would be a bit better. So you get these weird situations. So planning big projects right now is a bit more challenging. For instance, one of the things that happened in Python 3.9, if I recall, we changed the entire parser of the language. Different parser, which I'd like to describe as changing the wheels of a car that is moving. Not the best feeling.

If we had a two-year release, maybe it would be a bit better. So you get these weird situations. So planning big projects right now is a bit more challenging. For instance, one of the things that happened in Python 3.9, if I recall, we changed the entire parser of the language. Different parser, which I'd like to describe as changing the wheels of a car that is moving. Not the best feeling.

We could have some extra rest if that was a two-year release cadence and we didn't have to finish everything and all the validation in one year. I mean, this doesn't mean that it was rushed. It's just that we have to put more hours just because we wanted to make to the release. But on the other hand, like this, you know, it's humans making it.

We could have some extra rest if that was a two-year release cadence and we didn't have to finish everything and all the validation in one year. I mean, this doesn't mean that it was rushed. It's just that we have to put more hours just because we wanted to make to the release. But on the other hand, like this, you know, it's humans making it.

So even before when the situation was, like Lukasz was describing, the day of beta freeze, which is the moment when no new features can come in and only backfixes from that point on in the release, everybody was rushing their feature on the last day, you know, like, All the new features. Humans are humans, so it doesn't really matter.

So even before when the situation was, like Lukasz was describing, the day of beta freeze, which is the moment when no new features can come in and only backfixes from that point on in the release, everybody was rushing their feature on the last day, you know, like, All the new features. Humans are humans, so it doesn't really matter.

Certainly the heat has been raised a bit because right now it's released more often and the numbers are changing faster.

Certainly the heat has been raised a bit because right now it's released more often and the numbers are changing faster.

Yeah, psychologically speaking, that's a very good point, actually. I'm glad that you mentioned it.

Yeah, psychologically speaking, that's a very good point, actually. I'm glad that you mentioned it.

Because one of the things that happens when you release every two years or more, especially for a language that needs to evolve and needs to change things, and maybe doesn't have... I mean, we can add our backwards compatibility, don't get me wrong, but other languages like C++ clearly care even more. So for a language that changed this much,

Because one of the things that happens when you release every two years or more, especially for a language that needs to evolve and needs to change things, and maybe doesn't have... I mean, we can add our backwards compatibility, don't get me wrong, but other languages like C++ clearly care even more. So for a language that changed this much,