 OK, that is not Python on hardware newsletter. People see behind the curtain. That is not the Python on hardware newsletter. It's an infinite. This is what we see. Yeah, it's an infinity mirror. So as I convince our video processing application to go to the right browser, it did. Cool. Hey, did you know that this is live? Yeah. Is it live? That was a time tunnel. So this week you can check out the newsletter. There's a lot of stuff going on. There's a Python 312 release. Some people really pay close attention to these. Open hardware summit. It's open hardware month. You can check out the summit they announced probably in May and April or so. Lots of Raspberry Pi five news. And then the highlights from October fest where you can join in and do like a PR for circuit Python. We're participating, but check out all the projects. There is always too many to go over. A lot of neat ink and displays, lots of display stuff this week and more. But the news, I think the big news is because we have a sibling, which is micro Python. So the circuit Python is the big broad board support education. Easy to use. We're, you know, we wanted to go on everything. And micro Python is a core it's built on. If you're in the Linux world, you know, there's different flavors and Linux. There's like the kernel, which has like kernel and then everyone builds their thing distributions. So we're one of the supporters, both philosophically and financially for micro Python. So when we see a new release, we're excited because that means we can start doing integration. So Lady data, what were the big highlights for micro Python. That we're into that we're going to be adding upstreaming and more. Yes. So one thing to note is we do merge with upstream pretty common pretty often. And actually right now we are in the middle of doing an upstream merge. That is what Dan and Scott have been working on for the last couple of weeks. They're working very hard. People who've done merges and have a lot of merge conflicts. It's, you know, there's a lot of code that's shared, but there's also stuff that's gone different. And so it takes a lot of time, but we will be integrating one 21 into circuit Python. And I think I think the goal is to do it before we release nine beta circuit Python nine beta. Okay, so now you know, like, why is this important? Because this stuff will be some of it will affect us at circuit Python users. But what's interesting, I thought about this and we discussed this a couple of weeks ago is there's a lot of stylistic changes happen to micro Python that I think were inspired by circuit Python. Well, hopefully I think that we. Yeah, I think you're bi-directionally like there's there's stuff they're like, oh, this is a good idea. And then I'm sure there's things that are like, oh, we like the way you did this or like the way you can access things on USB drive or the naming convention. Yeah. So the big change is, you know, that is, it's making a difference in people's code is they're getting great of the you prefix built in modules. So used to have to import UOS instead of import OS and see Python would be called OS and in micro Python be UOS you was like micro and be like you storage or you, whatever, like you time. It's not a big deal, but it's it's not the same if you're learning Python and then you have to kind of say like, oh, for this you have to remember to do this. Yeah. And there's a couple of ways where they're doing it, but I think a lot of it is like, you know, trying to create more back and forth integration between see Python code and micro Python code because, you know, and this is something that we do a lot of the We'll run on a Raspberry Pi running see Python will go to desktop, which I think is really cool we'll have to write one driver one example code and you can use a temperature sensor and display on your, you know, desktop Mac on your Raspberry Pi on your single board computer, or on a Sam V 51 or RP 2040 and so I think that yeah this was one of the decisions we made really early that was a reason why we had to fork and have a different implementation this distribution, because micro Python was really like that we want to keep the prefix stuff and we're like we really don't want to keep the prefix stuff. And so we know we split there, but it's really great to see micro Python go with that same decision. I personally I think it's a great decision I think I think it's good to have my Python move in with circuit Python and it means that micro Python circuit Python is becoming a little bit more cross compatible. I mean, we're always merging upstream, and we contribute as well. But I think it's good to start stuff will be on different chips and if you go to circuit Python.org you can see all the different boards like micro Python as a specific set of boards they support we have. Yeah, other set. And then people make their own boards and they run their own businesses around it. For educators, it's hard to. You already have to make a bunch of choices, and it seems like if you're in the education space. People are learning Python. So this just makes it easier. So if you're learning Python or you're in a workshop setting, you're learning Python and then this makes it. You don't even have to remember me put a micro a little you or something. So it should help even like documentation. And if you can have code portability running on that new Raspberry Pi running on my ticket. Yeah. They, you know, ESP 32, they moved to idea five. That's actually something that we're also doing, which is kind of good idea five is going to support the newest ESP 32 chips. It's a big change, but micro Python and circuit Python both updated it. They added really support for Pico W which is great. We haven't done that in circuit Python yet, but we're thinking about it how we can do it. Import stuff has been treated to optimize. I think that's probably going to be, you know, that stuff, the core implementation, not for specific stuff does get merged into circuit Python. So we'll probably be able to benefit from their speed ups on importing. The edit ESP now I think we do to, you know, in circuit Python, we added a PR and they have a lower module as well. So, some good stuff, you know, I always tell people there are some things that micro Python supports that circuit Python doesn't and vice versa. There's space for both of us. Yeah. I mean, the good news is you can choose. There's a lot of electronics out there where you have to use their ID, their cloud thing, their thing, and you're kind of stuck with it. And once you're stuck with it, that's the end of it. It's nice to be able to run whatever you want to run, right, right tool, right job. Also experiment. MIT license. Try them all out. Great. So that is Python hardware news. You can get the newsletter every single week has all this and more deliver to your inbox. Totally separate site for daily dot com. The way you know for sure we are not going to spam you because we don't like spam even more than you don't like spam.