 Let's do some Python on hardware. Right, Blinka. OK, the Python on hardware newsletter this week, lead story. You can listen to a fantastic interview with Damian George, MicroPythonly. This is on the Invented FM podcast. Download it, read it, listen to it, do all the things. You can check out that on our website, on the Invented FM website, on any of the streaming services that you use that have hot-catching. I think I'll bundle up this into two pieces, because we're going to talk about the sort of Python day. But sort of the biggest news is you and the circuit Python team kind of made a decision a long time ago. So for the super beginner, there's a little you where there was a little you, Micro, in front of Python stuff. And that meant it's like, oh, this is a MicroPython thing. And we decided not to do that. Correct. And now MicroPython is also not doing that. Yay. Why did we not do that? Why is MicroPython not doing that? And why is this all good? Why is this better? Yay, we're doing the same stuff together. So one of the decisions that MicroPython made, and a lot of things about code is making decisions. And you stick with one, or you change your mind later. But they decided to go with UOS and UJson and U-Sys, putting the U in front of the library names, because they were customized to be for MicroPython. And there were a couple trade-offs with that. One, it made the code much smaller, because they could just shove functions that were necessary for MicroPython in any library that was convenient. However, the downside is that the code for MicroPython was no longer a true subset of CPython. So when you're doing import UOS and then like OS, UOS.mount, or whatever, you'd have to remember. You'd have to have different code, depending on whether it was running on CPython or on MicroPython. And while MicroPython was designed to be very fast light, one of the things that we wanted to do with CircuitPython is to make it as close as possible to CPython running on a microcontroller. And so we decided not to change any existing built-in functions in the libraries. We may not implement the entire capability of the library, but. NumPy or something like that. Yeah, we have MicroLab, which is a totally different thing. Like we don't say it's NumPy, because it's very different. NumPy is, of course, massive. But with stuff like OS versus UOS, we took out anything, like those, I think, would be like a real-time clock call. But if you learn Python once, you get to use it everywhere, essentially. Yeah, like instead of having the SD card mounting code. Because CPython doesn't really have SD cards. It's not a thing that happens with CPython. Like you have your built-in storage on your computer. You're not mounting a disk drive. Whereas with MicroPython, circuit Python, you do. And so those functions lived in UOS and made UOS like it was much more compact, where we pulled them out and put them into a new library called Storage. And we wanted to make it so that any code that you wrote as much as possible, we wanted to make it run on CPython or circuit Python. It's just a structural decision. So also, we have Blinka when you do stuff in Linux land. So that still all works. Yeah, and that's another thing. Almost all the examples for all of our libraries can run on a microcontroller or on a single board computer. There's another powerful thing. So now Python on microcontrollers, desktop Python, whatever you want to call it. CPython. CPython. And then pretty much the ways people are familiar with Python, they're learning online and classes or if they're reading books. All this stuff kind of work all the same now. Ideally, yeah, it's like you should be able to actually follow along with a Python class on a circuit playground express or something. There's nothing new like it should be as transparent and similar as possible. But the trade-off is, again, it's a little bit more bulky. But in my opinion, is chips only get bigger and faster? I remember what was it like six years ago or something? We talked about this. And I think we made a bet that chips are going to get faster, lower costs, and more storage. Because we show up as a USB drive, essentially. And we're like, well, pretty soon, it's just going to be like a full-on computer. So why don't we just assume, why don't we work back from this is going to be Python Python? So that's kind of big news. I think one of the cool things, too, is since schools are doing curriculum in Python, they can have a microcontroller. One of the bits of feedback that usually here is because they're like, well, I just don't want to type in a screen all day. You could do physical computing with something like a circuit playground express. And you can blink LEDs and you're learning Python. And you get the REPL. And you get all these things. And you don't have to remember different types of Python for microcontrollers. You just, if you know Python, you know Python. Sorry, that's kind of big news. Yeah, so a lot of the micro-python is doing the same thing. I think that's really, it's mature. It's all good. And Damien's great. Listen to the podcast. And then also just a little note. So someone had emailed Adafruit and said, oh, I want to do it. I'm not going to buy electronics, but I want to donate money to you because I like that you do open source. So do you know what? Micro-Python, we help with the fundraising each year to get people to sponsor the Micro-Python project on GitHub. And they're working towards their goal. We do a separate sponsorship in addition to the thing that's on GitHub because we're tight with them. We actually send them money. So I said, just donate to them because that's one of the things that Circle-Python's based on. A lot of people use Micro-Python. All these things work together. It's open source. Just like there's multiple flavors of Linux. You may not want to use one flavor for one thing, or you might want to use both, or you might want to use either. Yeah, some people would. It's great. Some people like Damien, some people. It's fantastic. You can choose and all of these things work together. Same kernel. Same kernel. Different distro. Yeah. So I suggested that and they did it. So that was cool. So the festivities, by the way, begin. Begins next week. Circle-Python Day is August 18. It starts at 10 in the morning. Circle-Python Day introduction with John Park, special edition 3D Hangouts with Noah Page and Liz. 11 AM, Beeps and Boops, Circle-Python Day panel discussion, hosted by Paul. 12.30, there's Circle-Python Day Game Jam with a foamy guy. There's the Matrix Portal board build with maker Melissa. There's Circle-Python Day Chat with Jeff, Dan, and Catney. There's special edition JP's workshop. There's Deep Dive with Scott. We're doing a show and tell. And there's Ask the Engineer. That's a full day. We're going to be in the Discord server. We're going to be broadcasting in all the places. It'll be super fun. It's super laid back. I know people still aren't traveling quite yet in stuff, or they're just starting to, or whatever. The timing never works out for people to hop on planes. Maybe we'll do a physical one. People do these around the world, but this is one place and you can watch all the live streams later. And that is our News of the Week. Again, next week, Circuit-Python Day. You can get the newsletter delivered every single week. Go to AdafruitDaily.com. Subscribe. We don't do anything with your email address. It's a completely separate site. Okay.