 Okay, hello everyone. This is the Circle Python weekly meeting for Monday, October 24, 2022. 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. Circuit Python is a version of Python designs around 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 any time by going to adafruit.it or you'll get a Discord invite to the group. You hold the meeting in the Circuit Python Dev Text Channel and the Circuit Python Voice Channel. The meeting typically happens on Mondays at 2pm US Eastern Time, 11am US Pacific Time, except when it coincides with the US holiday. There are a lot of US holidays on Mondays, so usually push it to Tuesday. In the Note Stock, there's a note to a calendar you can view online or add to your favorite calendar app. You 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. There's a Google notes doc that accompanies this meeting and recording. The notes document contains timestamps to go along with the video, so you can use the doc to view only the parts of the video that interest you the most. Meeting tends to run 45-60 minutes, so that having the timestamps lets you skip around. After each meeting, we post a link for the next meeting's notes document to the Circuit Python Dev Channel on the Adafruit Discord. And in particular, we pin that post to the pin messages in that channel, so you can always go to the pin and find a link to the latest Google doc. If you wish to participate but cannot attend, you can leave hug reports and status updates in the Note Stock for us to read during the meeting. This meeting is held in five parts. The first is Community News. This is a look at all things Circuit Python and Python on hardware in the community. It's a preview of our Python or microcontroller's newsletter. The second part is the state of Circuit Python libraries in Blinka. This is a quantitative overview of the entire project. It's a chance to look at the project separate from what we're all up to. Third part is hug reports. Hug reports is an opportunity to highlight the good things folks are doing, taking the time to recognize the awesome folks in our community. The fourth part is status updates. Status updates is an opportunity to sync up on what we've been up to. You can take a couple of minutes and talk about what you've been doing in the last week since the last meeting and what you'll be up to over the next week until the next meeting. And finally, the fifth part is in the weeds, which is an opportunity for more long-form discussions. These discussions might come out of something mentioned in status updates or be something you've identified ahead of time as too long for status updates. So that's how the meeting will go. I will now start with community news. And I'll read it. There's some stuff from the newsletter, which just came out. And I also added one new thing, which will be in the newsletter, but it's not yet. It's not in the draft. Okay. So CircuitPython 800-beta3 was released. It is relatively stable, but there will be further additions and fixes before the final release. Note that ESP32-C3 boards have not been functional since 800-beta2. So for those, use the absolute latest or use 800-beta1. And I'll just note that I expect to do a beta4 this week, like maybe in the next day or two. Python 3.11 has its general release today. There's a live stream on YouTube right now that's happening. For some reason, there aren't like precursors to that on the Python.org website, but this will definitely be mentioned in the newsletter. It just was not so clear that it was coming today, but I got pinged in the Python Discord about it, so I'll put that in. The RedMonk Programming Language Survey, which is a different, there are several different surveys of programming language usage. This one has Python at the number two spot after JavaScript. There's a link to the results in the notes doc. Oh, there you go. There's a graph. Somebody's posted. Thank you. So just to follow up on where this news comes from, the CircuitPython weekly newsletter, the CircuitPython community-run newsletter that's emailed every Tuesday, and is our editor, illustrious editor, does a fantastic job collecting things. The archives are available at AdafruitDaily.com. It highlights the latest Python and hardware-related news from around the web, including CircuitPython, Python, and RigorPython developments. You can contribute to this newsletter by submitting a pull request in GitHub. There are links in the notes doc. Or you can tag us with a tweet, hashtag CircuitPython on Twitter, or email cpnews at Adafruit.com. Any of those ways are great for sending things to the newsletter. So now I'll take a timestamp and we'll move on to the state of CircuitPython libraries in Blinka. As I mentioned, this is quantitative overview. So overall, in the past week, this is up to, like, Sunday night, we've had 34 pull requests merged by 18 authors, notably some authors I have not recognized before, Zanywup, Atalantor, maybe TWA 127 and DMAW 118. Thank you for your contributions, everyone, especially the new people who are on board. There were eight reviewers of these 34 pull requests, and overall, there were 37 issues closed by nine people and 16 opened by 13 people. And a bunch of issues were assigned the Hectoberfest label earlier in the month. So there are new assignments here. But if you're interested in contributing and earning Hectoberfest brownie points, which are good toward a shirt or a tree planted in your name, look for those issues that are labeled with Hectoberfest. So I could read the core, but Jeff, would you like to read the core since I'm reading everything else? Happy to. And I was just going to add about Hectoberfest, almost any accepted pull request in a CircuitPython-related repo is going to get you credits. Hectoberfest label, we applied to things that we think are more suited to a beginner, but pick up any issue or just pick up a pull request of your own devising. Anyway, but onto the core, which is the part of CircuitPython implemented in C. You typically load it via a UF2 file. We had 23 pull requests merged from 10 authors and five reviewers. And I just want to recognize again, Atlan, Tori, and not a new contributor, but a more recent contributor, Bill88T. Thank you all for your contributions. And thanks to our five reviewers outside of the Adafruit organization that's really just micro dev this time around. So we really appreciate that. In terms of pull requests, we have 13 open pull requests. A good half of them are open over 60 days. We think that we're waiting on activity from somebody else. But if you need something from us, please don't hesitate to comment or ping on those pull requests. And then as far as new requests, we have them coming in at a fairly good clip. We've got some open anywhere from zero to 37 days on the lower end of the spectrum. Issues-wise, we went down on issues with 28 closed by six people and eight opened by seven people. We've got 561 open issues. But in the core, we manage those by milestones, which are all about what Adafruit is prioritizing as far as development. And so before the 800 stable release, we have 26 open issues we would like to resolve. And during the 8XX release cycle of stable releases, we have a further 12 issues that we would like to resolve. There are three issues not assigned to milestones. So Dan or I will go through and just quickly do a gut check and assign those to one of those milestones. So as Dan was talking about, we continue to move toward the stable release of eight, but there is a lot more to do. I think this may be a record number of beta releases. It's certainly a lot to go to for beta releases. But we are going to continue to work on those open issues. We welcome anyone in the community working on those with us. And we just want to make eight a great release. We've got support for lots of new hardware for the web workflow. We really need you to check it out and kick the tires. If you don't mind trying out beta software. And yeah, the focus remains moving towards a stable release. And that's what I've got for the core. Okay. Thank you, Jeff. And I would just note, a lot of issues were closed. I went through some of the long-term issues and found a bunch that were stale or I decided that we would never do. But mostly they were stale or they had already actually already been fixed but not closed. So that's why there are so many. That's partly why so many more were closed that opened. Usually it's kind of a steady state. But we're long-term issues going below 500 has not happened for a while. I'm sure we'll go back up again. Okay. Let's move on to the library section and, Katnie, could you do that? Yep, absolutely. The section refers to all of the Adafruit Circuit Python libraries, which is anything that starts with Adafruit underscore circuit Python underscore, as well as a few extras such as our community bundle and our cookie cutter. Over all of these repos for the last week, we had eight pull requests merged by six authors and four reviewers. The oldest pull request merge was 77 days old, so I'm glad we're still getting through some older ones. The rest were 10 days or less. We currently have 31 open pull requests. We had seven closed issues by five people and eight opened by eight people, leaving us with 573 open issues. 106 of those are labeled good first issue as well as Hacktoberfest at the moment. And if you are 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, including all the open pull requests, all the open issues, and the issues you can search by label. So if you're interested in contributing code or documentation, check out that list. Open first issue is a great place to start if you have never done anything. We have a guide on contributing to Circuit Python using Git and GitHub, and we're always available on Discord to help you. If you're interested in reviewing, check out the open pull requests. If you have the hardware, test something, if you don't, take a look at the code, let us know what you think, and leave a comment. And that's a great way to get started, and once you're comfortable with that, we can talk about leveling you up to the review team. In terms of library updates in the last seven days, we had no new libraries, but a series of updated libraries that I will not read off, but they are available in the notes. And that's what I've got. Okay. Thank you, Katnick. Okay. Next up is our Blinka report. Makervelis is not here today, so I'll read that. Blinka is our compatibility layer for Circuit Python and single board computers like Raspberry Pi running Linux. So it is a library that lets you use Circuit Python code, but running with CPython, that is the sort of the standard regular Python. So in the past week, there were three pull requests merged by three authors. There was one reviewer, there are six open pull requests. Some of them are really old, some of them are not. Two issues were closed by one person, and no new issues were opened. There are right now 82 open issues in the Adafruit Blinka library. And there are currently 98 boards supported. So we're getting really close to having 100 of the single board computers supported under Blinka, which will be great when we get there. So watch for that. All right. So now I'll move on to Hub Reports. Hub Reports is 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're text-only or missing the meeting, but have Hub Reports in the notes document, I'll read them off as I get to you in the list. Okie dokie. So I'll start. I'd like to thank MicroDev and Jeff for insights into what the problem we had with the ESP32C3 bills not working at all. It turned out, well I'll talk about that in status about what the problem was. I'd like to thank Scott Tannout, who is on a pair run to leave right now, but is working on some projects at home I think and encountered an issue for one of his own projects and he actually contributed a fix. I was expecting to say, you know, you don't have to do it. I was going to say you don't have to do that, but if he's having fun, that's fine. And thanks to Jeff for continued addition to the PQW support in the past week. It's now getting even better and people are using it for all kinds of useful stuff right now. Next up is C Grover, who's text-only. C Grover thanks TechTrick for continuing support with community bundles submittals. Thanks to Todd Bot and DJ Devon3 for amazing Circuit Python eyeballs just in time for the pumpkins. Thanks to DJ Devon3 for heads-down work to sort out the APIs for their social media counter project. And thanks to Todd Bot and Paul Kettler for an interesting The Bootloader podcast today. Thanks for the editor advice. All right, and next up is DJ Devon. I would like to send a hug to PR Kettler and Jepler for their PR guidance. I was trying to submit a PR and they literally walked me through it. It was thanks, guys, that honestly really helped. To BlitzCityDIY for the Twitter Auth header API example, I know I mentioned that last week, but it still took me like two weeks to get through all of it. And because of the one example, I was able to just stroll right through off the rest of the APIs. I'd like to give a hugged report, I should say, to Jason Crack Developers for creating a wonderful VS Code extension that helped cut down my time swimming through thousands of lines of JSON with a neat visualizer tool. I can definitely recommend to anyone working with large JSON dumps. And to Jepler, who said, hold my beer, as he answered the question, can a Feather S3 run Doom? Okay, thank you, DJ Devon3. Next up, follow me, guy. All right, thanks, Dan. Last week, hugged reports, thank you to Jeff for all the improvements in PicoW, but in particular, fixed initiative that I found just a few days prior. So that was really cool to see that already working again. Thank you to Dan for continuing with all the beta releases and getting all of this new fixed versions and improvements out. Hugged report, thank you to Liz for joining the rotation to host this meeting. Definitely echoing what Dan said, it's really nice to get more and more folks doing it, and then a group hug to everybody. Thanks. Okay, thanks. Okay, next up, Jeff. Hello. So I wanted to thank you, DJ Devon, for being ready to learn more about GitHub and pull requests. To Katni, thanks for that long chat last week. We had plenty to catch up on. Mark Kudev, thank you for working on Cobraq. I've been kicking the tires more on that in my status updates. To Bill88T, thanks for picking up access mode, access point mode on the PyCow. And to Lady Aida and PT for recognition of my work on the PyCow project. Yeah, and that's what I've got for Hugged reports. All right, thank you. Okay, next up, Katni. Hello. So I want to give a hug report to Liz for joining the meeting host rotation. To Bruce for beginning steps to also join the meeting host rotation. To Jeff for a lovely chat. To Dan for all the release work. To Tammy makes things for a wonderful chat as well. To Tektrick for a meeting with me this evening. So I haven't done this yet, but early hug report to talk about a library CI PR that changes how the library CI works, possibly for the better. To Phil and Lamor for being understanding of me struggling mentally with COVID recovery and allowing me to focus on one major thing at a time. My list of things that I have to do is very overwhelming. And more was very specific that I should focus on one thing at a time. And it was a big relief and a group hug. Okay, thank you, Katni. All right, next up is Liz. Hello, sorry. Hugged report to Katni for reaching out to ask if I'd be interested in hosting a circuit pipeline meeting from time to time to prep for that. Today I'm running a local recording. Make sure I have all the technical things set up properly. And a group hug. Okay, thank you. That is also known as Blitz City DIY in Discord. Okay, next up is Mark Gambler, who's not here because he's getting a vaccine booster. It says, thanks to PT for starting Ask an Engineer with my eye video. It was cool to see it there. And a group hug after spending time back in our dreamer world. There was so much I miss about Circuit Python. So good job to everyone. Okay, thank you. All right, next is Paul Kudler, who's here. Thanks, Dan. I've got a hugged report for Tech Trick for the thorough pull request review. And it's really thorough and I appreciated it. And a group hug. All right, thank you. And next up is Tammy Makes, things who's not in the meeting right now. So I'll read theirs. Thanks to Katni for a great conversation this week and a group hug. And then finally, I'll also read Tech Tricks. But thanks to everyone here for teaching me about embedded systems. It helps secure a fantastic score on my grad courses bid term and a group hug. All right, that's great. All right. Next up is Status Updates. This is a chance for us to sync up with each other on what we're doing. I'll start and we'll go through the list alphabetically as before. You can, when I call on you, you'll take a few minutes to talk about what you've been doing since the last meeting and what you were planning to do until the next meeting. It's also an opportunity to provide tips and tricks relevant to what people are working on. If you'd like to discuss something, we can always move into the weeds. And also, if you have some non-circuit Python thing that still is of interest or is occupying your time or mental space, let us know if you'd like. OK, I'll start. I spent several days last week working on a problem that caused the ESP32 C3 builds not to work at all. I narrowed it down to an update in the GCC tool chain. The tool chain means all the programs associated with compiling and linking and producing a binary and that kind of thing for a particular architecture. There was like what seemed to be a minor update, but it caused the builds not to work at all. And kind of a group effort with Jeff and MicroDev, we figured out that the problem was that they had changed the default architecture. The ESP32 C3 is a RISC-5 chip, and there are several many variants on that, and they had changed the default variant to one with floating point, and that apparently caused the builds to break. So Jeff and MicroDev kind of jointly figured out what was going on here in terms of the architecture and then made a change and that fixed that. So this fix was not ready in time for 808, beta 3, but because we have these broken boards I'd like to release beta 4 really soon to at least get these boards working again and there will be some other minor fixes. Another thing I did was to add documentation on limitations about various features and modules in CircuitPython. So this information is really going to be a page in the Welcome to CircuitPython guide, but instead I've distributed it to the FAC and the Welcome to CircuitPython guide and then various board guides so that for instance the ESP32 S3 boards have some like Danger, Will Robinson kind of stuff in them about what is working and what is not working, and also various modules in the read-the-docs documentation will say like okay on this board this doesn't work or these boards don't support, we don't have a DAC so there's no analog out, that kind of thing. So I hope this will be helpful and will reduce the support load on everyone. After doing all that I'm back to fixing issues on 8.00, I'm working on some sleep issues right now. Okay that was a little long, let's go ahead with Cgrovers, who's text only today, submitted four more helpers to the Community Bundle working on three or four more before putting a fork in this activity and moving on to other projects and that is a not a GitHub fork. Okay, Git fork. Working on an approach to generalize the adaptive low-pass filter used in the ShadowWatcher light sensor gesture detector class, that is a lot of adjectives. Would be useful for noisy real-time sensor projects. This weekend was the annual rain gutter cleaning ritual, the two-story extension for the leaf blower that I picked up at a clearance sale made it easy to clear the gutters from the ground. The drawback is getting covered in debris as you look up to position the nozzle. It's a rite of passage, I guess. Okay, I can just visualize that. All right, next up is David Globe. I tested Beta 3 on a few devices, especially Pico W, hugged the Dan and Jettler, did some flip-clock test and PR, hugged the FOMI guy, Tetrick, maybe others, and acquired two Trinket M0s, two QDPI RP2040s and two Jiao RP2040s for future AT Maker use. USB host tricks. Okay, next up is DJ Devon 3. Go ahead. Okay, I submitted detailed feedback on the new user pages where multiple features were broken in Chrome and Firefox, and the Adafruit folks have fixed that, so now user pages are fully working in all browsers. I finished my seven-segment social media counter project. It uses four separate APIs in one script, which is pretty long, but the ESP32S2 handles it like a champ. I pushed a PR to the Adafruit Request Library to have them included as separate API examples and not just one long script. I split them apart and ensured every API was working separately, then pushed a PR. They're all waiting to be reviewed by some brave soul who must have a developer API account for each one of those sites to test to confirm that they're good to go through the PR. So good luck to whoever does that, and you have to like APIs. I put the finishing touches on the Neo Pixel goggle kit, recut the mirror lenses so they're not so bubbly around the edges anymore, and I accomplished my goal of making them a real wearable with slightly better aesthetics thanks to the mirror film. Started on a pumpkin for the Digi-Key Hack a Pumpkin Challenge tonight, which ends this Thursday, so for anybody else that's interested in participating in that, that ends this Thursday, I will be using my non-existent carving skills to gouge some lines for a couple of nudes. Since Ann went with the Space Coast theme for her Halloween project, I'll be responding with the Treasure Coast theme pumpkin. For those that don't know Florida Geography that well, the Space Coast and the Treasure Coast are regional neighbors. Turn Todd Bot's QT eyes into alligator eyes for my Halloween dragon mask that I'll be using to hand out candy this year. Because Halloween projects in Hacktoberfest have deadlines, I put up working on all of my other stuff until after Halloween, as probably most people are, and that's all I got. All right, thank you very much. Next up is Foamy Guy. All right, thanks, Dan. Last week, I submitted a PR in the HTTP server library to make it return smaller chunks to work around an issue that we noticed on the PicoW. I tested the fix inside the core for that actual issue, so we can also return larger chunks now as well. I built a display IO version of the trivia game. I've been working on a few different variations of this game using a free trivia API, so I built the display IO1. It's using a small 1.8-inch display and a 1 by 4 NEO key as the input. The game is fully functional. The player can select a category, select how many questions, and go through and answer the questions, and it will keep track of score. It'll let you play again when you have completed the game. In order to work on the category portion of that, I kind of extended a previously created list select widget to make it possible to scroll through lists that are too big to fit on the display. So it used to allow you to scroll through a list, and you had to have everything on the display, and now you can actually set how many you want to show, so you can scroll through an arbitrarily long list and let the user select a thing from it, which is exactly what I needed to choose the categories. This week, I've been doing some library PR reviews and testing this morning. I will be working on a different version of that trivia UI on a bigger screen. I got a 2.8-inch screen, so I'm going to use that because the small one was a bit cramped, and some of the longer answers and categories and things were getting cut off, so I think your screen will fit nicely. Once I'm happy with the UI there, I also want to try to make a container or a box or find a box and figure out how to mount this stuff inside of it, because I like to make a little self-contained handheld device that's based on this PicoW screen in the 1 by 4 NeoKey. And then the last thing I did yesterday is the Raspberry Pi PicoW inside of this industrial control button that I bought offline a while back, and I've got this set up now to send signals into my PC and then ultimately convert those signals into commands to send inside of a running Factorio server, which is a video game that's running on the PC, and this has allowed me to control things inside the video game using these nice big chunky buttons and the lock key and the panic button that are on this controller I got. So the first thing I did was use it as a launch button for the rocket inside the game. That was a lot of fun, and that's what I got. Thanks. OK, thank you. OK, next up is Jeff. Hi again. So last week, I ended up with a big list for last week, so bear with me. I ported Doom to the ESP32S3 Feather for a little gag video that Philby made. There is a link to that YouTube in the note stock. The bulk of the async IO fixes and improvements were merged, and so those are either out in the current beta or out in the next beta or out in CIRCUP updates. I fixed an obscure hard fault when assigning the trace back property of a generator exit object. It turns out as a memory optimization micropython and therefore CIRCUP Python keep one generator exit object around and throw it whenever a generator is told to stop. And this object is read-only, so you can't assign its trace back property. Now you get a correct exception. Next up, I fixed a bug on the PicoW where the use of GPIO pins attached to the Wi-Fi coprocessor could interfere with regular pins. And similarly, I fixed a bug where certain pins didn't work with PIO or other features that used PIO such as Pulse-IN. And again, those were both affecting the PicoW specifically. I implemented static network configuration on the PicoW. So if you need to work by setting your IPv4 address and your net mask and your DNS server and all those things manually, you can do that. I did a few tiny, tiny doc fixes, a few updates to the GitHub Actions build process of various Adafruit repos. GitHub has been deprecating various features and where we use those features directly or where we can upgrade an action so that it doesn't use that feature indirectly, I've been making some PRs to do that. I accepted multiple requests for USB PIDs in PidCodes.org, which I'm kind of the steward of while Scott is out. And I worked on a higher-level wrapper for programs for Coprock, which is currently living in a personal GitHub repo. Link is in the note stock. But with the Coprock module, I've discovered that I'm seeing a lot of crashes in CircuitPython while halting the coprocessor. And that's been a little bit of a thorn in my side. So I'd like to get that fixed. So moving into this week, my outlook is a little uncertain. My partner, who lives with me, tested positive for COVID yesterday after we had spent a lot of time in close contact. So it seems likely that I'm also going to be sick soon. She's doing OK. And we have a good support network here in case we need something, so no need for you to worry about us. My goals and hopes, though, are to continue with Coprock. And I've been promising this for at least three or four weeks. Running right the IBM PC keyboard adapter guide for the learn system and maybe squash some 800 bugs. But the odds I will get to all of that are very low. And that's what's up here. OK, thanks, Jeff. And I hope you either don't get sick or it's very brief. OK, next up is Katn. So last week, I caught up from being out for two weeks. Towards the end of that, I kept thinking of work stuff I wanted to do, but was totally unable to do it. So I added it to my to-do list. So the to-do list had a bunch of minor stuff at the beginning for me to try and get through on Monday. There's still a bunch of there, but I got through a lot of it. I finished up and put the LTR329 LTR303 guide into moderation. That got me through Thursday. And then Friday, I started the PCF 8575 guide. And then noticed that I had gotten way behind on my guide feedback. So I went through about 50 guide feedbacks. I'm still behind, but I tried to get through all the stuff that I could do quickly. So this week, update the Pico Circuit Python border definition to have STEMI squared C singleton for use with Pi Cowbells. The PCF 8575 guide plan on trying to finish that up. I'm waiting on Eva to finish a series of PCB repos for various boards. And then I will be emailing the new products team to add to the related products pages. The boards don't necessarily need guides, but folks always wanna see the schematic and board files for various things. So that way those are available, even though there's no guide. I have a bunch of miscellaneous and then a huge list of other stuff, but thankfully I've been told to focus on one thing at a time, so the PCF guide comes first. That is not entirely true at the moment. I'm still focusing on one thing, but I did get the next thing I'm going to be doing, which is the guide for the Pi Cowbell. The Proto Pi Cowbell. So there's no code to go with that, but we have a series of headers that work with it. So it will include pinouts and a list of assembly instructions with each type of header. So folks can know their options and get started with their Pi Cowbell. And that's what I've got. Okay, thank you, Katnie. And next up is Paul Cutler. Thanks, Dan. I finished my 32 by eight Neil Pixel audio reactive project this week that I've been working on for the last couple of months on and off. And then there's a new episode of the bootloader out today where Todd Bot talks a little bit about CircuitPython's micro lab and some more topics like code editors and 3D printing and a couple other things. Thanks. All right, thank you. Okay, then now I have two people who are text only. First, Tammy makes things. Started work on an idea for using CircuitPython to control my Novation Circuit grew box synth. This is going to require extending the Adafruit MIDI library to be able to generate MIDI N-R-P-N non-registered parameter number of messages. So we're searching what those look like on vacation for my birthday. So this week is going to be a bit chaotic. And then next step, I'll read TechTricks contributions. Last week, mostly housework at the light, like excited to pick up more CircuitPython things again, keeping up with some PRs, working on unified CI actions for the CircuitPython libraries. And this week, starting a Paceman helper library for dumping text using services like paceman.com, which could be helpful for dumping error texts or messages for applications where a screen or serial connection isn't wanted. Preparing for a very spooky community help desk on Halloween night, October 31st at 7 p.m. Eastern Standard Time to go over PRs and anything else people come up with. I'll try to find non-turing complete candy to snack on. Thanks, Jephler. That refers to the Zoom, I mean, the Doom candy bar video. And following through with a backlog of patches to the library, starting with unified composite actions, focusing on making sure all the contributions for Oktoberfest are counted and going to try to give a preliminary review now so changes can be made before the deadline. Generally taking a look at everything on my to-do list from before moving and spin it all back up again. If I owe you something, please let me know. And that wraps up our status reports for today. We'll move on to In the Weeds. I have a very minor thing to ask about this week. I was just wondering whether people, right now the video for the weekly meeting shows Discord, it shows the Sugar Pie Van Dev channel and Discord. And I was wondering if people thought it would be helpful. Whenever I run the meeting, I'm always scrolling the weekly meeting notes, obviously, because I have to read from them a lot. And I was wondering if, suppose we show Discord and the notes side-by-side in the video, would that be useful for people who are reviewing the meeting on YouTube? I don't- I'm not sure how readable it would be at that point because you're squishing two of them in the same screen. Yeah. And the other thing I would say is folks seem to love to click around and the tag for each person's animal, folks that aren't logged in, shows up and blocks the text a bunch. I'm not sure it's necessary. We link to it and it's got timestamps. I think that's more important. Okay. Because I just feel like it doesn't help the podcast at all and folks may be watching the video as well, but the first thing in the YouTube notes is a link to the notes document. That's a good point. So they just bring up the notes and follow the timestamps. Yeah, yeah. Okay, that sounds reasonable. I won't, it's just more work. So we don't have to do it. That's fine. Okay. If there's no other in the weeds, we'll wrap up for this week. So next week is the meeting will be at the regular time on Monday, October 31st. Today has been the Circular Python Weekly for Monday, October 24th. Thank you everyone who participated. Remember, if you wanna support Adafruit and CircuitPython and those of us who work on CircuitPython, consider purchasing from the Adafruit shop at adafruit.com. The video of this meeting will be released on YouTube at youtube.com slash Adafruit and the podcast will be available on major podcast services. There will also be links to this meeting in the Python for Microcontrollers newsletter, which is coming down tomorrow. Visit adafruitdaily.com to subscribe. As I mentioned, the next meeting will be next Monday. It's Halloween in the U.S. and most places that celebrate Halloween, October 31st, 2 p.m. U.S. Eastern, 11 a.m. Pacific. Remember, the meeting is held on the Adafruit Discord. You can go to adafruit.it slash discord. And if you wanna be notified about the meeting, ask to be added to the AdScience Circuit Pythonistas role on Discord. So we hope to see or hear from all of you next week. Thank you everyone. Thanks everyone. I will stop recording.