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

Pablo Galindo

👤 Person
238 total appearances

Appearances Over Time

Podcast Appearances

very funky interpreter when like you know you call a method on something sometimes like another method is called because like there was something like a memory reordering problem which is a very technical like deep thing right but like like and debugging that particular thing is just hard but like that is very rare and obviously we fix it immediately

very funky interpreter when like you know you call a method on something sometimes like another method is called because like there was something like a memory reordering problem which is a very technical like deep thing right but like like and debugging that particular thing is just hard but like that is very rare and obviously we fix it immediately

and we are really surprised about first how many people have jumped at this and they're super excited and they want all of those extensions and working and second how quote-unquote stable this is like meaning that how little bags we have seen in the wild like we expected many many many more right and we are seeing very little so so right now it's super super promising yeah like what what does help is that we do have the people behind it like some girls who actually did the prototype of 39 and then 312

and we are really surprised about first how many people have jumped at this and they're super excited and they want all of those extensions and working and second how quote-unquote stable this is like meaning that how little bags we have seen in the wild like we expected many many many more right and we are seeing very little so so right now it's super super promising yeah like what what does help is that we do have the people behind it like some girls who actually did the prototype of 39 and then 312

It depends, right? If they are paid to make sure that the thing is stable, the recommendation is no. I mean, try it out, sure. You can get very excited, by the way. One of the things that we have seen, me, myself, right? For instance, I'm at the company I work, Bloomberg. is that we have tried to see what will happen.

It depends, right? If they are paid to make sure that the thing is stable, the recommendation is no. I mean, try it out, sure. You can get very excited, by the way. One of the things that we have seen, me, myself, right? For instance, I'm at the company I work, Bloomberg. is that we have tried to see what will happen.

Even if it crashes every three months, whatever it is, but just to see a sense of what is the improvement here. Because if then down the line you're going to justify any effort on your side to adapt your thing to the free-threaded version, it's really good that you know what you're going to gain.

Even if it crashes every three months, whatever it is, but just to see a sense of what is the improvement here. Because if then down the line you're going to justify any effort on your side to adapt your thing to the free-threaded version, it's really good that you know what you're going to gain.

So that for sure, trying, we really want people to try and tell us what they see and what doesn't work. Is this a production-ready workload? Absolutely not. Not because we know it's going to crash or anything, but because we don't know the real status of the thing, right? We take stability very, very seriously in the core team, so we are not comfortable right now.

So that for sure, trying, we really want people to try and tell us what they see and what doesn't work. Is this a production-ready workload? Absolutely not. Not because we know it's going to crash or anything, but because we don't know the real status of the thing, right? We take stability very, very seriously in the core team, so we are not comfortable right now.

That's why the thing is called experimental. Because we are not comfortable right now recommending people, especially when you not only have the interpreter, but all these other things. And still we need to figure out good APIs for those extensions to hook into the interpreter and things like that. And that is not there. right now.

That's why the thing is called experimental. Because we are not comfortable right now recommending people, especially when you not only have the interpreter, but all these other things. And still we need to figure out good APIs for those extensions to hook into the interpreter and things like that. And that is not there. right now.

So the chances that we can look at these things and say, yeah, this can run in production, no problem, is almost zero right now. But as we release Python 3.14 and 15, we will move this experimental into supported, which means that you can run it in production, but it still will be two versions.

So the chances that we can look at these things and say, yeah, this can run in production, no problem, is almost zero right now. But as we release Python 3.14 and 15, we will move this experimental into supported, which means that you can run it in production, but it still will be two versions.

And eventually, when we gain enough confidence that this is the future we all wanted, it will be only one Python, which will be Python without the free-threaded version. But until we call it stable and, you know, supported as the keyword supported, I wouldn't recommend people to actually use it in production environments.

And eventually, when we gain enough confidence that this is the future we all wanted, it will be only one Python, which will be Python without the free-threaded version. But until we call it stable and, you know, supported as the keyword supported, I wouldn't recommend people to actually use it in production environments.

As a clarification also for the people that don't know, PyPy is not a JIT for CPython. It's an entirely different interpreter. So it's like the same language, but it's just a different interpreter written actually in Python, which is JITed then. But it's a separate thing.

As a clarification also for the people that don't know, PyPy is not a JIT for CPython. It's an entirely different interpreter. So it's like the same language, but it's just a different interpreter written actually in Python, which is JITed then. But it's a separate thing.

Well, one of the things that is very exciting with the JIT right now is that the approach itself is quite cool.

Well, one of the things that is very exciting with the JIT right now is that the approach itself is quite cool.