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

Łukasz Langa

👤 Person
198 total appearances

Appearances Over Time

Podcast Appearances

And it turns out that the infrastructure that the big Linux distributions have, like Ubuntu and like Red Hat, is extremely useful for us to early find bugs in a new version that we are developing in the betas, in the release candidates, and so on.

And it turns out that the infrastructure that the big Linux distributions have, like Ubuntu and like Red Hat, is extremely useful for us to early find bugs in a new version that we are developing in the betas, in the release candidates, and so on.

So it would be worthwhile if we could actually ship the newest version of Python with those Linux distributions as they are also developed and go through their respective betas and so on. That's also great for the end user, right? Because then by your autumn release of Fedora, you are released with the newest version of Python that was just released. That is a great experience for the end user.

So it would be worthwhile if we could actually ship the newest version of Python with those Linux distributions as they are also developed and go through their respective betas and so on. That's also great for the end user, right? Because then by your autumn release of Fedora, you are released with the newest version of Python that was just released. That is a great experience for the end user.

So I... wrote a Python enhancement proposal document arguing those things that I'm just telling you, that it would be amazing to have a fixed release cadence that we can trust and share with the Linux distributions such that they can essentially rely on us having certain milestones in the release, like reaching beta one, like reaching release candidate one.

So I... wrote a Python enhancement proposal document arguing those things that I'm just telling you, that it would be amazing to have a fixed release cadence that we can trust and share with the Linux distributions such that they can essentially rely on us having certain milestones in the release, like reaching beta one, like reaching release candidate one.

so that they can use the latest version as soon as possible. And we switched to the release cadence in Python 3.9, and we've been using it ever since. So yeah, Your Honor, that's my position on this issue.

so that they can use the latest version as soon as possible. And we switched to the release cadence in Python 3.9, and we've been using it ever since. So yeah, Your Honor, that's my position on this issue.

I guess for compiled languages that might in fact work better, for us the difference is that we're interpreted. So there's a lot of code that is lying next to your interpreter and then you're trying to run it with whatever is available to you. With a lot of the libraries that we're supporting, they're a particular issue. So now I'm going to be the devil's advocate because Pablo was too apologetic.

I guess for compiled languages that might in fact work better, for us the difference is that we're interpreted. So there's a lot of code that is lying next to your interpreter and then you're trying to run it with whatever is available to you. With a lot of the libraries that we're supporting, they're a particular issue. So now I'm going to be the devil's advocate because Pablo was too apologetic.

Wow, wow. Sounds right. Yeah, let me just say like, hey, this is all a compromise, you know, and there's obviously going to be things that are better and things that are worse. The price to be paid for shorter release cadences is that the matrix of tests of CI that a library maintainer has to now kind of suffer with, has to run, is larger, right?

Wow, wow. Sounds right. Yeah, let me just say like, hey, this is all a compromise, you know, and there's obviously going to be things that are better and things that are worse. The price to be paid for shorter release cadences is that the matrix of tests of CI that a library maintainer has to now kind of suffer with, has to run, is larger, right?

Because the number of versions that is out there that people are using, there's just more versions than there were before, right? You had 2.7 and 3.6 maybe, and then 3.7 appeared some 18 or 19 months later, so... then the growth of this matrix was sort of spread out in time. Now that matrix is bigger.

Because the number of versions that is out there that people are using, there's just more versions than there were before, right? You had 2.7 and 3.6 maybe, and then 3.7 appeared some 18 or 19 months later, so... then the growth of this matrix was sort of spread out in time. Now that matrix is bigger.

I would claim that, okay, it's good that we're testing with every particular version to identify where an incompatibility arose or something. However, I always like to say that it's still the same sausage. We're still the same sort of team that is developing the thing. We still have the same velocity, only we slice it thinner now.

I would claim that, okay, it's good that we're testing with every particular version to identify where an incompatibility arose or something. However, I always like to say that it's still the same sausage. We're still the same sort of team that is developing the thing. We still have the same velocity, only we slice it thinner now.

So every release is easier to migrate to compared to the last release because necessarily there were fewer changes.

So every release is easier to migrate to compared to the last release because necessarily there were fewer changes.

I want to add one thing. So NumPy is not doing as well as Pablo is claiming. They're doing way better. There are already wheels for Python 3.13. Before the release of Python 3.13, those wheels are going to work on the final version of Python 3.13 released October 1st. We're releasing this like mid-September. They're already there. Moreover, they're also already there for the specific version

I want to add one thing. So NumPy is not doing as well as Pablo is claiming. They're doing way better. There are already wheels for Python 3.13. Before the release of Python 3.13, those wheels are going to work on the final version of Python 3.13 released October 1st. We're releasing this like mid-September. They're already there. Moreover, they're also already there for the specific version