 Hello everyone. This is the Circuit Python weekly meeting for Monday, May 15th, 2023. This is the time of the week where we get together to talk about all things Circuit Python. I'm Dan and I'm sponsored by Adafruit to work on Circuit Python. You might ask, what is Circuit Python? It's a version of Python designed to run on tiny computers called microcontrollers. Circuit Python development is primarily sponsored by Adafruit, so if you want to support Adafruit and Circuit Python, consider purchasing hardware from Adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join anytime by going to get an invite from adafru.it slash discord. We hold the meeting in the Circuit Python Dev text channel and the Circuit Python voice channel on the Adafruit Discord server. Typically this meeting happens on Mondays at US 2 p.m. Eastern time, 11 a.m. Pacific time, except when it coincides with the US holiday. In the Notes doc there's a link to a calendar you can view online or add to your favorite calendar app. We also send notifications about upcoming meetings via Discord. If you would like to receive these notifications, ask us to add you to the AdSign Circuit Pythonistas Discord role. So I mentioned the Notes document. There is a Google doc which we use to accompany the meeting and recording. That's available in the pinned messages in Circuit Python Dev. Let me just pop that up to show you. And then before the meeting, if you can add notes to that, that would be great and then we'll read that or you can read it. And the final Notes document gets time stamps included to go along with the video so you can use the document to skip around and view the parts of the video that interest you most. The meeting tends to run 3 to 45 minutes, maybe up to an hour sometimes. After each meeting we post a link for the next meeting's Notes document to the Circuit Python Dev channel and pin it, as I showed you. If you wish to participate but cannot attend, you can leave hug reports and status updates in the document for us to read during the meeting. This meeting is held in five parts. I'll explain each part when I get to them. The first is community news. The second is the state of Circuit Python libraries. And the link of the third is hug reports. The fourth is status updates. And the fifth part, which may be empty, is in the weeds where we might have some longer discussions. So with that, we'll get started with community news. And let me silence my phone because it just beeped. Okie dokie. And get my timestamp working. Ok. So these community news is available from the weekly Circuit Python for Microchip News newsletter, which I'll tell you about later. So this news is called from that. So as of last week, there are now over 400 Circuit Python-compatible microcontroller boards, which is amazing. Those are listed on CircuitPython.org. There was a large addition this past week. They include board from many manufacturers. There are boards from the community, some companies that are not Adafruit, and entire new businesses and makers using and shipping boards with CircuitPython. Supported chips include chips from Espressif, Microchip Sandy Line, Nordic Semiconductor, NXP, RP2040 from Raspberry Pi, ST Chips from the ST company, IMX from NXP, and more. Ok. So NXP makes the IMX chips. The growth of CircuitPython-compatible boards since 2017, there's a chart of that. It's interesting that it's been less than a year since 300 boards, which is about two boards per week, which is fabulous growth. And I'll just note that we add Adafruit boards, boards that are made by Adafruit, or boards that are other manufacturers' boards that Adafruit sells. But if you would like to add a board, we have a whole guide on that about how to add a board. You can find it in the Learn Guides, and we welcome community contributions either from the makers of the board or from a community member who wants to add a board that whose manufacturer is not working on adding the board. Ok. Next up, Hackaday Supercon 2023 is on. Hackaday Supercon is going to run in 2023 and will take place November 3rd to 5th in Pasadena, California, in the U.S. The conference organizers will like to hear your proposals for talks and workshops. There's a call for speakers and the note stuck, and there's a blog entry about it. Read all about it. Ok. Another interesting thing that came up. Frequen, which is a Lora-based open-wan network. There's something in the note stock about it. Frequen is an effort to create a Lora-based open-wan network completely independent from the internet and the cellular phone network. It is coded in a micro-piphone with an XS1276 Lora chip driver. It is possible to send encrypted messages that will reach only other users with a matching symmetric key. Frequen also implements its own very small, lossless, and impressed 1-bit images. I don't know what a 1-bit image is, as proof of a concept that can send small media types over a Lora. I have a lot of 1-bit images when I eat crackers and get crumbs on my desk. Next up, using micro-piphone to get started with AWS IoT Core. You can now use micro-piphone to get started with AWS IoT Core with a recent guide by Amazon. Prototype your project to quickly test the full IoT solution. Micro-piphone makes it easy to connect the device to AWS IoT Core and route messages to other AWS services. This is very interesting to use micro-piphone and maybe somebody's also interested in taking a look at this and see if it could be adapted for Circuit Python or whether we already have support in the guide. I do not remember. I think we may have something about that. All these news items came from the Circuit Python Weekly newsletter, also known as the Python or Microcontroller's newsletter. They are complete archives in AdafruitDaily.com, and this newsletter comes out weekly. It highlights the latest Python and hardware related news from around the web, including Circuit Python, Python, and Micro-Python developments. You can contribute news to this newsletter. You can submit a poll request to GitHub. There's a link to the GitHub where the draft, which is handled on GitHub, in the note stock. You can also tag a tweet with hashtag Circuit Python on Twitter and probably on Maston also, and you can email cpnews at Adafruit.com. Any of those ways are great to get news to us. We don't really care what you choose. All right, let's move on to the next section, which is the state of Circuit Python, the libraries, and Blinka. We're going to go through a quantitative overview of the entire project. It will give us a chance to look at the health of the project, separate some of our qualitative status updates. We'll talk about the project overall and then separately discuss the core libraries in Blinka. First of all, overall, in the past week, there were 60 poll requests merged by 25 authors. Some people that I don't have recognized might be new or who have contributed. In the past, Peter, I5 or L5, not sure, 100 Visions guy, Stefan Fluss, C. Guardia, Tyath, Virtual Radish, Muddy900, Furbrain, Bojan Pototnik, Kangos Gal, and Pedro of 16. Sorry if I've mispronounced your GitHub username, but these are all people I don't recognize. They may have been there before, but I'd like to recognize any new contributors. Thank you very much. So I said 25 authors, there were 12 reviewers, and there were 42 closed issues by 11 people and 22 open by 20 people. So that's really great. We've got a lot of closed issues here. So next up, we'll talk about the Circuit Python core and Scott, are you available to read about the core? If not, I can hop in. Go ahead, Scott. Yeah, I think Scott's not muted, but maybe have more microphone trouble. Okay. All right, so this next section pertains to the core of Circuit Python, which is the part written in C that makes the stuff go. And over the last week, we had 19 poll requests merged from 12 authors and four reviewers. So thank you to all of those folks. That leaves us with 20 open poll requests ranging in range from 1 to 453 days old, although those oldest couple are in draft status. And if you do have an open poll request, like I do, we encourage you to go back, check in if there's something waiting for your action to go ahead and do that. And if you need any help finishing that poll request, please feel free to ping us. We'd love to help and get some of those older poll requests closed out. On to issues. We were slightly down with 13 closed issues by six people and nine new issues, excuse me, 10 new issues open by nine people. So that's net minus three. I won't bother telling you the total number of open issues because it is a big number. Instead, I'll talk to you about milestones. Adafruit manages the Adafruit people's time by assigning issues to milestones. And so for the 810 release, which will be our upcoming stable release, there are three open issues we'd like to solve. For the 8XX series, we've got 28 open issues. Those are bug fixes or improvements that we deem compatible enough to go into a minor version. And then for the next major version, 900, we've identified 29 things that we'd like to do. Typically those are breaking changes. And we'll be mentioning some of those a little further down because we're getting pretty close to releasing 810 final. And subsequent to that, we will make the main branch before version 9 development. Anyway, other milestones, we have 543 long term issues. And those are issues that aren't prioritized for Adafruit folk to work on right now, but we always welcome people in the community. If you have an itch there that you want to scratch, if you want to learn to contribute to the core, you can take a look at those long term issues. They aren't all intractably difficult. It's just that they aren't prioritized for Adafruit folk to work on. And we've got 5 issues not assigned to milestone. And so that may indicate that the core developers need to get together and decide if there are some of those to put on our version number milestones or whether to put those on the long term milestone. And that wraps things up for the core. Back to you, Dan. Okay, thank you, Jeff. Okay, next up is State of the Libraries and Katny, could you read that? Absolutely. So, this section applies to all of the Adafruit Circuit Python libraries, which is everything that starts with Adafruit underscore circuit python underscore, as well as the community bundle and a few extras such as our cookie cutter. And across all of those repositories, we have 37 pull requests merged from 13 different authors and 10 reviewers. Part of the number of PRs that we merged this week is related to we updated the version of Pylon to cross all of the libraries so that it works with Python 3.11. So, there's a patch that does most of that automatically, but there's always a few that slip through and so that increased the number. And the cookie cutter PRs are usually we have to update the cookie cutter, so all future libraries also have the update. And that leaves us with 67 open pull requests, which is about where we were last week. So, I would say that most of what's in this list was related to the update. We had 27 issues closed by five people and 12 opened by 11 people, leaving 604 open issues. 51 of those are labeled good first issue. If you're interested in contributing to Circuit Python on the Python side of things, check out circuitpython.org slash contributing. You'll find all of this information and more. If you're interested in reviewing, check out the open PRs, take a look at the code, if you have the hardware, test it. If you don't, just leave us a comment, let us know what you think. And once you're comfortable with that, we can talk about leveling you up to the review team. If you're interested in contributing code or documentation or bug fixes, etc., check out the list of open issues. They are all available by library. You can search by label if you're new to everything. Good first issue is a great place to start. And don't let the process intimidate you. We have a guide on contributing to Circuit Python using Git and GitHub, as well as the fact that we're always available on Discord to help you. So we want to make sure you can contribute in a way that works for you. So library PyPI weekly download stats, total library PyPI downloads over 311 libraries was 119,313. And there is a list of the top 10 library downloads that I won't read off, but I will say all of them are over 1000 this week, which is not typically the case. So there's been a lot of activity. In terms of library updates in the last seven days, we have three new libraries, Circuit Python AXP192, Circuit Python BMP581, and Circuit Python STTS22H. And all three of these are community bundle libraries. And that's where we are with the libraries. All right. Thank you, Katny. All right. Next up is the state of Blinka. And, Melissa, if you're available for that, go ahead. Yeah, I'm here. This week we had Blinka's our Circuit Python compatibility layer for MicroPython, Raspberry Pi, and other single board computers. This week, we had four pull requests merged by three authors and three reviewers. They're current. We're down to two open pull requests now for amongst all the repositories that are Blinka-related. There were two closed issues by one person and zero open by zero people, leaving a net of 96 open issues. There were 15,603 Pi PI downloads in last week, 9,528 Pi wheels downloads in the last month, and we are now up to 120 boards, just a lot of that's due to community members contributing boards. And that's where we're at. All right. Thank you, Melissa. Yeah, I remember when it was 100 boards. So 120 is fantastic. Yeah, it was like 101 just a couple weeks ago too. That's great. All right. Okay, next up is hug reports. So hug reports is not bug reports. It's hug reports. It's a chance to highlight folks in the Circuit Python community and beyond for doing awesome things. I'll start and then we'll go down the list alphabetically to give everyone a chance to participate. If you've noted the notes that you're text only or you're not in the meeting, I'll just read your notes when I get to them in the list. So we'll start with me. So I'd like to thank Jeff Epler for continuing to work on Synth.io, which is making getting a lot of people very excited. And there are all kinds of already great demos based on the capabilities that he's adding to Synth.io. We're looking at really like a wonderful basis for using Circuit Python to do audio, synth and music synthesis. Okay. Next, thanks to T. Hess, who's continuing to contribute PRs and looking at bugs that are associated with various network related issues. I really, really appreciate that. That's Ted Hess. And thanks to Scott for suggesting last week that, by the way, we look like we were about ready for an 8.1.0 release, which I hadn't seen the light at the end of the tunnel. And now I see it. And I really appreciate that. Okay. Next up is C. Grover. I'll read theirs. Thanks to Jeff Epler and the team of testers for Synth.io. I was blown away when the foundational building blocks emerged and was utterly amazed when I heard polyphony envelopes and effects. Next up is DJ Devin. Go ahead. Thank you. I have a hug for Tyus for helping with an algorithm. He entered, well, I wrote the algorithm and he entered the script into chat GTP, GPT, which spit out a 99% correct answer. The only thing it got wrong was trying to import Numpy NumPy instead of ULab NumPy. And I no longer see chat GPT as an evil overlord, but as a relatively helpful tool. Thanks to Foamy Guy and Nairdark for an interesting conversation about REST APIs, what they are, what they do, etc. And a hug to Lady Aida and PT for dealing with Facebook incorrectly tagging show and tell as hate speech this week. And a group hug for everyone who doesn't engage in hate speech, which is everyone. All right. Thank you, DJ Devin. I have some like brief kibitzing about chat GPT. So, yes, you can use chat PT, but be extremely careful. It can be very confident and still be completely wrong. And it'd be interesting to see a more specialized, like, you can make your own chat GPT models. It would be interesting to see if we just fed the learn guides, the only the learn guides into something into a chat made a language model with, you know, selected content. We might get fewer mistakes, for instance. I took it with a grain of salt and was able to like kind of take what it spit out and modify it and actually use it. And it, it all, it does work. Right. That was great. And you just have to say like, just because it's, it says it's right, doesn't mean it's right. And everybody use it with that in that way. Yeah, it's, it's, it's hard to describe, but you have to like be prepared to modify whatever it gives you. Right. Exactly. Okay. All right. Next up is Foamy Guy. All right. Thanks, Dan. Hard reports for me this week. Thank you to Bill, 88 T and anecdote, who both helped me troubleshoot some issues I was seeing this morning with Wi-Fi, including testing it out on their own on debug builds to try to confirm whether or not they were seeing the same thing. I really appreciate that. It's outside of our community, but a hard report for me goes out to net ninja on YouTube. I've been following their view JS tutorial, basic view JS tutorial on YouTube, and I've found it to be a nice resource. And they actually have loads of other tutorials as well. Although this is the first time that I've found them, but it's great content. And then a hard report, thanks to maker Melissa for a point or two, confirm the behavior around the periods on the 14 by four segment display. It treats those a little bit specially. And I need to go back and test that again with some of the changes I submitted. And that's what I have for this week. Thanks. All right. Thank you. All right. Next up is Jepler. I have to find my unmute button. Hello. So I have a hug for you, Dan, for doing so much to bring 810 to stable and for offering to do one of the upcoming micro Python merges once we've started working on version nine. A big thanks to Todd Bot for making some demos showcasing Cynthia. Oh, I know those were getting some play on mastodon and on hacker news. So bringing people teaching people about what's coming up and hopefully getting them excited as well. And finally to JP Todd, but again, mark for feedback on the next direction for Cynthia, which I will talk about a little bit later when we get to status updates. And that's what I got. All right. Thank you. And next up is Catty. Hello. So first up, thanks to Tectric for updating pilot and black across all the libraries and fixing up the ones that had issues with the new versions. Hug report to FOMI guy for looking into an issue with one of our projects or with all of our projects on read the docs to Jeff for a ton of help with my current project code to you Dan for going through it to make sure I didn't leave any test prints in there and questioning my logic as well. Um, to FOMI guy for talking through a very specific circuit Python feature and whether it would work on a very silly project idea. Um, spoiler alert, it does so silly project may be happening. Um, to Naradoc for more help with my code to bill 88 T for a bunch of help with a Wi-Fi issue in my code and to Scott for adding the inky frame to the circuit Python core and a group hug. All right. Thanks a lot. Um, and then, uh, Melissa, if you're available, go ahead. I just had a group hug. All right. Thank you. Okay. Next is Mark, um, known as gambler 21, who's not, uh, here. So I'll read theirs. Thanks to Todd bot for answering some synth questions about a couple of YouTube videos he made. And thanks to Jeffler for all the synth work, the depth of what I can do is mind blowing. So is the math behind it. Okay. Uh, next is Carter, who's text only. Thanks to Tetric and Catney for heads up on, uh, continuous CI, that is continuous integration, uh, deprecation, needing attention in hybrid Arduino library repos. And thanks to Eva for updating all the repos for the above. So yes, we, there's a lot of maintenance that goes on in the libraries having to do with just preventing bit rot or compensating for bit rot in the library, uh, CI stuff. And next up is Scott. All right. Can you hear me now? Yep. Yeah, sweet. Somehow my setting got changed. Um, okay. So for hunger boards, just a quick one for Joshua from tiny vision AI who was cheering me on for, uh, adding support for the Pico ice to circuit Python. It's a board with a RP 2040 connected up to an ice 40, uh, up 5k, which is a, a well supported FPGA on an open source world, which is cool. So Joshua has been a help with that and they're continuing to help me with it. So thanks to them. All right. Thank you. And then finally, I'll read Tetric's, uh, he's out right now. Thanks to Dan H. Jose David, uh, uh, Catney and foamy guy for PR reviews last week for helping with reading recent passage patches. Yes. Tetric submitted like a bazillion, uh, updates, housekeeping updates to the libraries. And a bunch of us reviewed those and approved them and a group hug. Tetric says, okay. Next up, we've got status updates. So what is status updates? Status updates is our time to tell folks what we're up to individually. I'll start again. It's as we did before, and we'll go through the list alphabetically. When I call on you, you can take a couple of minutes to talk about what you've been doing since the last meeting and what you'll be doing until the next meeting. This isn't also an opportunity to provide tips and tricks relevant to what people are working on. If the discussion comes too long for status updates, we can move it to in the weeds. So I will get started. Um, so I was, uh, I came back from a, a trip, uh, last Tuesday, so I've only been working since Wednesday or so and can't just catching up on things. But, um, late last week, I've been finishing off the last, as many final issues as I could for 810. Um, I fixed a bunch of rather specific bugs, that people had submitted that were somewhere old and somewhere new. Um, so we're down to, uh, three issues. Two of those are kind of related and we might push those forward to 8XX because that issue, it has to do with network crashes and we're still debugging it and it's not a regression, it's a regression from 7, but not from 8.0, unfortunately. So we might just push that forward. And I did a lot of reviews and as I mentioned, I did a bunch of reviews of the housekeeping, library housekeeping, uh, poll requests. All right, uh, next up is C Grover. Um, I've been running a three-ring PCB design and built Circus Laylia haven't been coding much. Nine more boards through Assemble followed by two new designs to send to Osh Park. After that, we'll put all the boards back into the clown car, take down the tent and move on to wrapping up some Circuit Python coding projects and associated guides. All right, great. Next up is DJ Devon. Uh, this week I wrote a basic algorithm, algorithm for temperature bias adjusting the BME280 sensor module. This is just the, the out-of-fruit module, not the one that's like on the boards or like the TFT boards. Um, but it was all Tyeth and Chat GPT who slimmed it down to a linear algorithm into like 10 lines of code. Um, I've calibrated the bias against mercury thermometers and the bias adjustment now makes the BME280 super precise to within a tenth of a degree no matter what the PCB temperature or the module PCB temperature is. It's almost as accurate as a mercury thermometer. The algorithm only needs to go down to 50 degrees to Fahrenheit below that. The PCB is sufficiently cooled and doesn't affect the reading. The algorithm is a work in progress. The more data points in the curve that I can feed it, the more accurate it becomes. By default, the BME280 is about 96% accurate, which that means there's an eight degree deviation when over 110 degrees Fahrenheit. Some of you up north might not reach that. In Florida, that's a yearly, like that's, it's just a matter of time. Uh, my algorithm brings the accuracy up to 99.1% and I'm shooting for 99.9% this summer. And since I'm in Florida, I'm in a good position to track these data points needed above 110 Fahrenheit. I went on show and tell this week with a feather DVI weather station, which I plan on using during a live stream or two live stream during hurricanes until I lose Wi-Fi or power. I tested my first live stream showing me organizing the GUI elements, which is kind of cool if you want to watch that. You can actually see Blanka like reloading in the background over the on-screen display stuff. I have a new project on the horizon using an itsy-bitsy NRF 52A40 with Seagrover's itsy-bitsy adapter and Adafruit Connect mobile app to control an LED candle through different colors. I thought about using WLED at first, but after staying all the different hoops you have to jump through, I just decided to go with Circuit Python and the NRF 52. So that's what I'm going to be doing this week and that's all I got. All right. Thanks for that extensive update. All right. Next up is Foamy Guy. All right. I, over the past week or so, validated a change that we put into the core a little while back that fixed some issues in the RTD docs pages where they don't, like some of the interactive elements don't work, like search and the pop-up for the versions. So I tested that, fixed the same one we did in the core out on the library to confirm that would fix over there as well and then passed that over to TechTrick to get it ready to go out with a patch to the rest of the libraries and it was successful. So that's in motion now. I, over this past weekend, I created an HTTP API for initializing and controlling RGB LEDs. In particular, it supports Neopixels and .stars right now and you can basically connect to it with get and post requests and just send it JSON data to tell it like which pins you want to initialize and how many pixels and things like that. And currently it has control to set all the pixels individually or use the fill functionality as well as like all the other properties like brightness and auto right and things like that. In the future, I'd like to add support for some of the existing LED animations to it. So you can, instead of setting everything to a solid color or something, you'll be able to tell it to start up, you know, the fade animation or one of the other ones. I finally was dragged my feet for a week or so on the non-blocking marquee scrolling for the HT 16K33, but I did finally get that submitted, although I do have some more testing to carry out. I, this morning, set up a Feather S2 TFT running an HTTP server to try to catch a hard fault that I was thinking was related to running the HTTP server and actually breaking news on that about five or six minutes ago, it did finally hard fault with the debugger running. So I actually have the stack trace from that. Now I just got to debug it and post it back up in issue later. And the last thing that I am up to which is outside the circuit Python world sort of is I'm trying to learn the basics of Vue.js. However, the reason, the motivation for trying to learn it is to be able to tinker with the edu blocks project which does kind of tie it back to circuit Python a bit. But that's what I have got going on. Thanks. All right. Thanks very much. All right. Next up is Jeff. Hello. So the main thing over the last week was improvements to Synth.io and the pull request, I think that was merged late last week, adds tremolo, vibrato, frequency sweep and rig modulation. And we've been having a little discussion in a thread here alongside circuit Python dev. Anybody's welcome to join us and have opinions. But adding LFO objects that can be connected in some kind of topology is a sensible next step. I started the implementation this morning and it's close to the point where I can try to hook it up in a way that it actually replaces the original tremolo and vibrato controls with controllable LFOs. And then JP and Todd Bodd and anybody else who cares to can kick the tires on that. I'm hoping that I'll get a PR in tomorrow. I haven't tested this on a hardware yet. It's just a bunch of C code runs into testing environment, but it seems to be in pretty good shape when I started my meetings this morning. And I also made a lot of progress on my Xerox A20 CPM machine and I'm working on a passive adapter board for a PC34 pin floppy connector to the 39 pin connector on the Xerox drive box that would hypothetically let the Adafruit floppy Featherwing interact with the contents of these eight inch floppies. And I did put a blog post up about the machine. I'll drop a link to that a photo. And then I also asked Chad GPT what is under the yellow sticker on the upcoming Arduino. And I think it came up with some great ideas. So I'm just going to share those with you as well. So another Chad GPT item. And that's what I got. All right. Thank you. All right. Next up is Katnie. Hello. So last week I finally figured out that the issue with my canary nightlight code is that there's some problem with it and ESP32-S2 but that it works flawlessly on ESP32-S3. So the project now uses the S3 QT Pi. Related, I should probably still try my code on a different ESP32-S2 to make sure I don't have a bad board. That said, if it is still present, someone should probably look into why it fails so spectacularly. And that person will not be me, though I'm happy to test it. So finally wrapped up the canary nightlight code, which was so satisfying. There is now a STEM and QT connector on one of our feather wings, but it turns out there was never a guide in the first place. So we're writing the guide instead of just doing a STEM and QT update. So I started that guide and then started the guide for the canary nightlight. I updated the guide I updated two guides. One is the M7. There's specific PWM audio capable pins and that's in there. And then the RGB matrix shield. It had a new revision, so that's been fixed as well. So for this week in no particular order, I do as much of the feather wing guide as I can without the hardware. Should be here tomorrow. Finish up my part in the canary nightlight guide so that I'm not blocking Noah when he's ready to finish it. I'm going to be doing the new Chalk Neo Key breakout guide. Miscellaneous, a couple of guide updates, some guide fixes, and there's three more of those in my to-do list here. And as time permits, I do have some project stuff I want to eventually work on and or document write up some guides there, but there's been a lot of other priorities. So those are probably going to remain background stuff. And in other news, my brand new laptop started its first day of work. This morning, I decided to do a fresh install. So we'll see how this goes. Previous laptop is still ready to rescue things if needed, but I'm super excited. That's what I've got. All right. Thank you so much. Okay. Next up is maker Melissa. Hello. Let's sit here. My, I can't read the documents. Like the text is going to weird. I need to, can you come back to me? I'm going to reload. Sure. No problem. All right. Scott, can you go ahead? Yeah, totally. So I have two libraries that I need to wrap up. One is the Jason stream, which I'm using for this eink or ePaper weather display. Jason stream allows you to process Jason as it comes in, or as it streams in. So it reduces the amount of memory you need to use. It's not super fast, but it is helpful for memory. And then also prompts toolkit, which I'm using for the circuit pirate and note that the circuit pirate will is going to be renamed. We'll look at circuit pirate. This week, I'm going to look into adding circuit pirate support for ice 40 image loading and probably SWD as well. So this might be the chance for as to be able to use circuit Python as an SWD probe. And LaMoure wants to use it just to be able to load images straight from circuit Python. I also want to circle back to USB host on the IMX and do a bit of testing because I saw that TAC was working on it. So I want to follow along with that and kind of support him. If I have a chance, I'll circle back to the continuing IMX testing and I have this learn guide about porting that I need to get back to. Lastly, I made a PR for the inky frame 57. It's merged in and I'm using it here, which is nice. And I also made a prototype branch for the Pico ice board, which is an RP 2040 combined with an ice 45 K, which is an FPGA. And I got one of those boards and so I made the board death for that. So that'll be cool. And that's my update. All right. Thank you. All right. Melissa, are you all set? Yes. It's looking correct now. Okay. Let's see. Last week, I finished adding a bunch of blinker boards to circuit python.org putting set 120 boards. I finished updating the code for my collaboration project airing. I updated platform detects so it now decodes the Raspberry Pi revision code and intelligently determines the appropriate board. This will make it much less work to manage every time Raspberry Pi updates a board. Also makes adding new boards easier. I fixed some issues with the Raspberry Pi installer scripts, but the peers are still open. And I fixed the links for the RP 2040 Feather thinking on circuit python.org. I'm not sure if that's been merged or not yet. And I worked on a so this week, I'm going to work on the cloud project guide. And there's going to be and I'll work on some more issues, get the issues, and get back to improvements for like the Blinka repo and stuff. And that's it. All right. Thank you. Okay. And finally, Techfix out. I'll read theirs. Last week, updated pylon and other pinned versions of pre-commit tools across the libraries fixed an issue with the cookie cutter where community bundles would be missing a new line. Submitted a PR to the core to build the steps package and updated more recent method. Submitting a patch for review that will finish updating pylon for a deprecation warning as well as fix an issue with jQuery that when we got implemented. And this week, Techfix will continue to look through a backlog of issues to complete and look at to making some issues to the learn guide repo to speed up the CI checks. All right. Well, that's it. For status updates, we don't have any in the weeds unless anybody has anything they'd like to bring up. So I will wrap up. Take a timestamp. So just to recapitulate, this has been the Circuit Python weekly for Monday, May 15th, 2023. Thank you everyone who participated, whether in person or by entering your notes. Remember that if you want to support Adafruit and Circuit Python and those that work of us that work on Circuit Python, consider purchasing from the Adafruit shop and Adafruit.com. The video of this meeting will be released on YouTube at YouTube.com slash Adafruit in a little while and the podcast will be available on major podcast services. It will also be featured in the Python for Microcontrollers newsletter which will be coming out tomorrow. Visit AdafruitDaily.subscribe to subscribe. Next meeting. Next week. No, not next week. Never mind. Next week is at a regular time. Next meeting will be held Monday as usual at 2 p.m. Eastern, 11 a.m. Pacific. The meeting in two weeks is delayed because of a U.S. holiday. But we'll talk about that next week. The meeting is held on the Adafruit Discord which you can join by going to adafru.it slash discord to be notified about the meeting and any changes to the time or day you can ask to be added to the AdSign Circuit Pythonistas role on Discord. So we hope to see you all next week. Thanks for your contributions this week. Thank you everybody for attending or contributing. Okay, thanks everyone. I will stop recording.