 Hello, everyone, and welcome to the Circuit Python Weekly Meeting for May 9th, 2022. It's the time of week that we get together to talk about all things Circuit Python. I'm Jeff, and Adafruit sponsors me to work on Circuit Python. Circuit Python is a version of Python designed to run on tiny computers called microcontrollers. Circuit Python development is sponsored primarily by Adafruit. To support them and Circuit Python, consider purchasing hardware from Adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join us any time by going to adafru.it-discord. We hold the meeting in the Circuit Python DevTex channel and the Circuit Python Voice channel. This meeting typically happens on Mondays at 2 p.m. Eastern, 11 a.m. Pacific, except when it coincides with the U.S. holiday. In the Note Stock, 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 Circuit Python East Discord role. There is also a notes document to accompany the meeting and recording. The notes document, after the meeting, contains time stamps, so you can use it to view only the parts of the video that interest you the most. And after each meeting, we will post a link to the next meeting's notes in the Circuit Python Dev channel on the Adafruit Discord. Check the pin messages to find the latest notes, Doc, so you can add your notes for the following meeting any time during the week. And just a reminder, if you wish to participate but cannot attend, you can absolutely leave your hug reports and status updates in the document for us to read during the meeting. The meeting is held in five parts. After this introduction, we go to Community News and take a look at the Circuit Python and Python on a hardware newsletter preview. Next up after that is the state of Circuit Python, the libraries, and Blinka, where we take a statistical overview of the entire project. It's a chance to look at the project by the numbers separate from what we're individually up to. Up after that is our first round robin section, hug reports, an opportunity for you to highlight the good things that folks are doing, and take the time to recognize awesome folks in our community. Next up after that is status updates. In this round robin section, we have an opportunity to sync up on what everybody's up to. Take a couple of minutes to tell us what you've been doing since we last talked, as well as what you'll be up to over the next week or until the next meeting. And then the last part, if we need it, is called in the weeds. This is an opportunity for more long-firm discussion. And this can either be something that you've been itching to talk about all week or something that comes out of status updates. Either way, we take that section in the order it is in the document, and we prefer that you add your topics as soon as you become aware of them. And that covers how the meeting will go. I am going to start giving you a preview of the newsletter. So first up, nine years of MicroPython contributions. Matt Terini used Gorse to look at the development history of MicroPython over its nine-year history. And there is a link in the notes document to a YouTube video where you can see that. And if somebody can paste these links into the channel as well, that would be super cool. Next up, the Risk Five CEO seeks world domination by winning over the likes of Intel. The CEO of Risk Five's governing body says she wants nothing less than world domination for the rising open source processor technology. But to do that, the nonprofit needs buy-in from a variety of organizations, even those steeped in dominant proprietary architectures such as x86 giant Intel. Risk Five has more than 2,400 members, including companies, universities, and government-related entities. And next up in MicroPython and Risk Five News, there is a new MicroPython port for the WCHCH32V307 microcontroller. It has been posted on GitHub. And there is also a link to our blog entry about it. So check that out. And more MicroPython adjacent news. The chip shortage is going on. And we've got this little series on YouTube called Chip Shortage. It's got a nice little jingle, but it's a serious topic. Anyway, last week's subject was the STM32F405 microcontroller, which is used on MicroPython's Pie Board, as well as other Python on microcontroller projects. And this video is basically an ask to ST for them to supply MicroPython with the quantities that they need of this crucial part. Now, the fun stuff. If you can make projects during the chip shortage, we've got a couple of Star Wars projects because that is in honor of May the 4th. And I guess also Revenge of the 6th. So first up, a Death Star animation in Circuit Python on a round LCD driven by the Adafruit QT Pie. That is from Twitter, our own Todd Bot. And I think this is another Todd Bot. Also for Star Wars Day, I made a silly targeting computer gizmo in Circuit Python. This one uses the ESP32S2TFT Feather, but can be adapted to other Circuit Python capable boards. And there are a bunch more projects in the newsletter. So we are, of course, inviting you to sign up for it. The Circuit Python Weekly newsletter is a community run newsletter emailed every Tuesday. The complete archives are at adafruitdaily.com slash category slash Circuit Python. We always aim to highlight the latest Python on hardware related news from around the web, including Python, Circuit Python, and MicroPython developments. To contribute your own project or news, edit next week's draft on GitHub and submit a pull request with the changes. You can also tag your tweets with hashtag CircuitPython on Twitter or email cpnews at adafruit.com. And of course, to subscribe to the newsletter, head right now to adafruitdaily.com and on the front page, you will find some links to subscribe. If you do it right now at the time of recording, you can get the newsletter tomorrow. And that runs it up for the preview of the newsletter. Next up is the state of Circuit Python, the libraries, and Blanca. Thanks to our very own Adabot, we gather statistics over the previous seven days and then break it down a little bit. So I will take the overall section in which we had 42 pull requests merged from 23 authors. I'm pretty sure 23 authors is a record or a near record. And Catney's gonna tell us a little more about why that is up later. In terms of reviewers, we had 10 reviewers, a lot of the usual suspects. But particularly, thank you to Tektrick, I think who picked up some of this extra load. And issues wise, we saw 35 issues closed by 14 people. And 21 opened by 17 people. So we've got good activity on both sides and we managed to decrease our overall number of issues, which is great. And with that, I will pass the talking stick to Dan to tell us what is going on in the core of Circuit Python. Thank you, Dan. Okay, thank you, Jeff. So in the past week, we've had 18 pull requests merged from nine authors. DuPont, GU, and Bill VanLuin, 424 are new. Thank you very much. And MWislead submitted their second one in only two weeks. Thank you also. There were five reviewers. Thanks to everyone, including Dave Putz, who is keeping a good idea. Hi on things. There are 18 open pull requests. A bunch of these are either drafts or being held for 800. We're not really behind where there are all, many of them are in abeyance waiting something else. There were 17 closed issues by two people and seven opened by five people. So that's a nice decrease in the number of closed issues in the core. There are now 519 open issues in the core. In terms of milestones, the 730 milestone has only four open issues. Three of those are actual bugs the other is housekeeping. So we're getting down to the wire on getting toward a release candidate for 730, which is great for 7XX in general. There are 28 issues we'd hoped to finish before the end of seven. And there are 12 issues for 800, which we will not work on until we start to work on 800. I'll stop there. Thanks very much. All right, thanks Dan. And in the near future, that section will go back to Scott. So we're looking forward to that, but letting him spin up a little bit slowly. With that, I will invite Catney to tell us about the libraries. Thanks, Jeff. So this section covers all the Adafruit Circuit Python libraries, which is everything that starts with Adafruit underscore, CircuitPython underscore, as well as a few extras, such as the community bundle and our cookie cutter. We had 22 pull requests merged from 15 different authors. A number of these folks are new, and I will talk about them in just a few minutes. We had seven reviewers as well, and thank you to all of our reviewers for facilitating all of our new contributors. We had, like I said, 22 pull request merged, leaving us with 29 open pull requests. We had 15 closed issues by 11 people and 11 open by 11 people. So we are down a tiny bit there, leaving us with 635 open issues across all those repositories. 194 of those are labeled good first issue. If you're interested in contributing to CircuitPython on the Python side of things, or you want to contribute documentation, check out circuitpython.org slash contributing. You'll find all of this information and more, including all the, a list of all the available issues, which if you're new to everything, you can check out the good first issues. We also have a guide on contributing to CircuitPython using Git and GitHub, so don't let that part intimidate you. And you can also search for bug or enhancement if you're looking for something a little more complicated. In terms of library updates in the last seven days, there were no new libraries, but there were a number of updated libraries, which I will not read off. And I want to thank the following folks for all their work at the PyCon US 2022 CircuitPython sprints. And these are the new folks that I was referring to earlier in terms of contributors. A word for that. J.Cerise, Matland, Dav Clark, R.M. Blau, Sabidam32, KT Kinsey37, and Ryan S. Keith. Between them, they submitted 14 pull requests, which I've listed below. And while many ended up choosing sort of hard mode libraries to work with, everyone was persistent and persevered. Everyone said they felt like they learned something and accomplished something, which is really the most important part of it to me. So I was really glad to hear that. And I was a little concerned as things were going because of the fact that they coincidentally picked libraries that were much harder to work with. I was concerned that their experience wouldn't be as positive as it might have been with something that was a little easier to accomplish. But it was very clear that these folks were interested in challenges and ended up coming out very well in the end. So I hope to see some submissions from these folks again in the future, but I really appreciate everything they did during the sprints. And that's what I've got. Thank you, Kenny. I'm still a little jealous I could not stick around for the sprints. It sounds like it was a very good time. It was pretty excellent. Anyway, then to round out this section, Macro Melissa, would you tell us what is up with Blinka? Hello, yes. So this Blinka is our circuit Python compatibility layer for Macro Python, Raspberry Pi, and other single board computers. And this week we had two pull requests merged by two authors and two reviewers. There are currently five open pull requests. There were three closed issues by two people and three open by two people, leaving a net of 77 open issues. There were 9,417 pi wheels downloads in the last month. And we are currently supporting 88 boards. And that's it. All right, thank you, Melissa. So next up is Hug Reports. As I mentioned earlier, this is the moment that we take to appreciate people in the community around us and beyond. And it is done as a round robin, so I will start. And then I will go through the rest of the notes in the order that they are in the document. So I was a little bit disorganized as I prepared for the meeting, so all I have for y'all is a group hug. And then I have notes from Ask Patrick W, who writes, thanks to Purples and Naridoc for their input and guidance on my Wemos C3 new board pull request, which is ready for review. And there is a link in the notes document. And next up, what is up, Dan? OK, sorry. I'm spacing out. Thanks to Catney and you, Jeff, Maker Melissa, Crayola, and Tech Trick for a fantastic circuit Python presence at PyCon. Worked out really well. Thanks to O Marshmallow from Espressif for a fix for an ESP32 I2C delay issue. They were very helpful in working with me, going back and forth with test programs. And they found a nice, found an obvious, not obvious, bug, but a clear bug. Thanks to Dave Putz for continuing to be an expert in pulse IO, reviewing and fixing things related to that. That's great. It takes a load off of us core developers. And thanks to you, Jeff, for lots of reviews in the past week. We came back with all throttles running from PyCon. And thank you. And welcome back to Scott. OK. All right. Thank you. I'm going to read notes from David, and then it will be FomyGuy up after that. David has a hug for Tammy Makes Things for an interesting stream and professional Python. All right. And FomyGuy has a whole list. I can see it right here. All right. Yeah. Thank you, Jeff. First up, Tammy Makes Things, who pointed me towards a feature inside PyCharm called Scopes, which turned out to be the exact thing that I was just wishing that I had. It basically kind of lets you hide all but the most important stuff in a project when you sit down to work on a given thing. So that's really nice. To Warrior of Wire for guidance and helping me make some changes to vector IO inside the core. Paul SK for sharing a more advanced tab layout example over on the Discord, which has multiple different data sources to show on the different tabs. And it also has a hot plug functionality for Stemma sensors, so you can kind of plug in, unplug, and it will notice and update the display accordingly. To reiterate what Katni said, all of our new folks that did contribute during PyCon, it is all the same list of names here. So I'll skip reading the names, the same ones that Katni read, but I definitely appreciate all of these folks and had a great time getting to work alongside some of them to do the reviews and such. To go along with those folks at PyCon, thank you to Tech Trick for helping do the reviews, as well as submitting some PRs of his own. Thank you to Neridoc, who also helped with some of the reviews and came up with a potential solution to save some space on CPX builds, which was kind of tied to one of those PyCon PRs. And then, lastly, thank you, of course, to Katni and Micro Melissa for being present there and just interacting with folks and helping get people involved and contributing and playing around with Cirque Python. Thanks. Thank you. And next with a huge list of things to be thankful for is Katni. Yep, here I am. So a huge hug to everyone who attended the PyCon US 2022 Open Spaces and Sprints. Thank you for joining us to learn and contribute. Special thanks to all the folks I listed off in the State of the Library section earlier in this meeting for contributing PRs from the Sprints. To PyCon US 2022 itself for all the effort put into keeping attendees safe to the best of their ability, my experience was much more amazing because I at least felt safe in the conference space. To Lukash Longa for an excellent keynote, as well as a couple of nice discussions, one of them to answer a question about Black with a great explanation as to the why. To all my old friends, all my new friends, and other amazing folks I met while I was attending the conference, thank you for helping make the Python community so great. To FOMI Guy for being available with help with the type hint PRs at the Sprints, a few folks watched your live stream during the Sprints and found it super helpful. I couldn't have facilitated the Sprints without you. Tectric for coming to visit us at PyCon, it was lovely to meet you and spend time with you. To Naradoc, Tectric, and Dan H were helping out in the CircuitPython Dev Channel during Sprints. Again, I would have struggled to handle some of the questions without the three of you helping as well. I think I said this before, but another thanks to Keith the EE for testing, updating, removing incompatible changes and ensuring that every example possible from PyCon 2019 was available to folks for PyCon 2022 to use on their Circuit Playground Blue Fruits. I couldn't have hosted the open spaces without this help. To Foamy Guy for putting together a list of the new authors from the Sprints and the PRs they submitted. To Tectric for putting together a script to update the pre-config.yaml file across the libraries. And a group hug to the community for being so welcoming and amazing to the new folks who joined us over the last week and a half at PyCon. Many folks commented how great the community was as a new person. And finally, another group hug to anyone I missed. Thank you so much, Catney. And next up is Liz, hello. Hello, I wanted to do a hug report for Scott returning from parental leave. To Jeff for an excellent PyCon blog post and also I hope you enjoy your upcoming trip. Delayed hug report I missed last week to be able to share. To Foamy Guy for excellent streams in general, but also the one two weeks ago where your code was lost, you handled that so well live and it was just a very reliable moment, I think a good moment for everyone in the community. To Catney for creating the VL53 L4CD fritzing object and for the upcoming fritzing training. And to Catney and Maker Melissa for all the excellent work at PyCon and group hug to the community. All right, thank you, Liz. Oh, were you done? I was just saying that's it. Okay, all right. Well, next up is Maker Melissa and then Tammy makes things. Hello. So I wanted to start out with giving a hug report to everyone who attended PyCon US that I got to meet. Everyone who kept the usual things going while I was at PyCon. You, Jeff, for your PyCon write up also it was really great to meet you. Thank you. In person. And a welcome back to Scott and group hug to everyone else. All right, next up, Tammy. Tammy makes things. Hi, so sort of an on the fly group hug that I forgot to put in the doc for everybody who attended PyCon. I'm sorry, I missed it and hopefully I'll get to be there next year and meet some of you. And then a group hug to the community. Thank you. And now, oh, not quite rounding out the section is Scott. Hi, Scott. Long time no see. Hello, yeah. So for those who missed it I've been out the last six weeks doing the first portion of my parental leave. So obviously the first hug report goes to my partner in crime, Becca Minigree is her handle on GitHub, who did an awesome job giving birth to our son Ari on March 25th. So she's been doing a great job since then as well, of course. Her hugs also to Becca's family and my family who have supported us through these last, last weeks and that really helped us get through the first few weeks are the toughest or they're a huge transition. So they helped to get through that. Thanks to Lamar and Phil for supporting me through the paternity leave. So they did pay for this stint, which is awesome. And everybody should have lots of paternity leave and maternity leave because it's important. So thanks to Dan, Katnay, Jeff and Tim for running the meeting without me. Thanks for Tim continuing the deep dives while I'm out and getting settled too. We'll have to have some discussion about what the plan is going forward, but I don't. I literally like barely opened up my email until this morning, so I'm very much ramping up. And then lastly, everyone in the circumventing community, I did listen to the meeting from last week while I changed a diaper during it and it's just been amazing to me. The little lurking that I've done, just how much things have been growing and continuing and Picon sounds like it was awesome too. So just thank you to everybody. It's really cool to see that circuit python is bigger and better even without me. So thank you all. All right, thank you Scott. It's good to have you back. And last up, I have some notes from Tech Trick. So Tech Trick writes a hug to DeShipu and Jebler for help thoroughly answering my circuit python question related to PRs. To Jebler again for all the updates and guides on the RP2040 PIO. Reading guides and PRs has been instrumental in using it for my job. I'd love to know more. Hug to Sik R. I'm sorry if that name was butchered for submitting a PR to my circuit python CSV library in the community bundle to add an example. I'm thrilled it has been useful to others. A hug for Fummy Guy for taking on and getting through a ton of PRs from Picon as well as offering to help take a look at what I'm reviewing now. I hug to Ketney for providing fun library infrastructure challenges to solve always with clear instruction and examples to make it easy to accomplish. Another hug to Ketney and also to maker Melissa for facilitating the sprint for facilitating the sprints at Picon and everyone who submitted a PR for the Picon sprints. They were a ton of fun to review and everyone was super awesome to work with. And last up is a group hug. And that leads us to the end of that section and to the beginning of status updates in which I have to move mine to the top of the list since I'm the host. All right, so with status updates we want to hear about what you've been up to since we last chatted and what you hope to get up to in the immediate future. And I will start out. So the last week I continued on the background right for the RP2 state machine. I wrote some additional examples and I've been documenting those within the learn system in pages that will be published soon. So this week I'm just wrapping up getting those items documented on learn and I am waited excitedly for the Event Horizon Telescope Press Conference on May the 12th. It is likely that they will show us the first picture of the black hole at the center of our own galaxy. And I'm trying not to leave too many loose ends or start anything too involved because soon I am out from May 14th to June 26th. We will be taking an international trip and crossing our fingers that everything goes well and smoothly. And I look forward to catching up with you people. It'll basically be July when I talk to you next though. So yeah, that's what is up for me. And next up is Dan. Okay. Thank you, Jeff. So over the weekend I incorporated a fix from Espressif for I2C issues on the ESP32, various ESP32 chips. I'm investigating another I2C issue which might have to do with repeated start or clock stretching on the ESP32 S3. As I mentioned, we only have a few bugs left before 730 RC0, the RC0 release. So we hope to do something with those soon. And I'm working on a test suite to test the basic functionality of a sort of Python port which will involve a lot of manual checking but try to automate as much of that as possible. That's in my, I'll put a link in it's, if you're interested in it, it's in my collection of repos right now. Okay. All right, thank you. Next up, I have a number of items to read. So first, in document order, David writes, finished a working version of my texture injector for Game Maker Garage, the Switch game. And there's a link to Twitter that it looks like somebody maybe will paste into Discord. Otherwise check the note stock. Anecdata writes, I'll be scarce on and off through the summer due to extra projects, events, and travel focusing on Discord support, GitHub, and maybe small PRs. AskPatrickW writes, past me, my Wemos C3 new board PR is ready for review. And future me, plan to make notes for FOMI guys deep dive last week. I'm going to be remote slash offline for the next month on an epic camping Airbnb road trip in the Southwest US. So if I seem gone, I'm only gone temporarily. I'm bringing the Wemos board with me so I can work that PR if needed. I'm very jealous. I love the Southwest. All right, next up is FOMI guy. All right, thanks, Jeff. So over the past week or so, I've been doing lots of testing and reviewing of the PRs mostly that came in through PyCon last weekend or the weekend before at this point. I don't know, whenever that was. I will be doing some more testing on that stuff this afternoon. I've been making my next pass through all of those today and I have a couple lined up to test this afternoon. If anybody is particularly interested, I'll be playing with the RFM radios, RFM9X radios, and also a fan driver. And I'll probably turn the stream on for a bit this afternoon while I work on that stuff. Couple other things I did get done is I've finished up the touch interaction for the tab layout widget that I've been working on for display IO and I got the PR created for that. So that's out there. Now I have an item to follow up on that but the initial code is in and good finally. So that's exciting. And then the other thing I kind of got into this week was back into the core vector IO, trying to make the shapes be able to be hidden when the group that they're inside of gets hidden. There needs to be a little bit of changes in there to make that work. And I had some success on that this week. So that was exciting as well. All right, thanks. All right, up next is Catney and then maker Melissa. Hello. So last week I got home from Picon US 2022 on Wednesday. A short recap. I attended the education summit on Thursday before the conference. I gave a talk called Simplicity and Fun Learning with Circuit Python. There's a link in the notes to the slides. I also did mini sprints, which was an intro to Circuit Python on the Circuit Playground Blue Fruit. It's same as open spaces basically, but shorter. During the conference, I hosted three open spaces with Jeff and Melissa, which is an introduction to Circuit Python on the Circuit Playground Blue Fruit. Scheduled two hours instead of one at the excellent suggestion of a community member ahead of time. They were well attended, even relative to other open spaces. We were running out of room. There were 36 chairs in the room, according to Jeff, and we gave up our own seats for attendees to make space for everyone. Two of the attendees of open spaces wrote games for the Circuit Playground Blue Fruit and submitted them to the Picon 2022 repo and there is a link to those examples in the notes. The sprints, I hosted two days, which was after the conference Monday and Tuesday. And we received 14 PRs from eight new authors. Everyone felt like they learned a lot and accomplished something. Many attended the first day, less on the second day, which is expected. And even though folks chose hard mode libraries, they all persisted, persevered, and succeeded. As for overall, I saw friends for the first time in three years and it was more needed than I realized. Made new friends, met a bunch of amazing new people. I felt like I was able to introduce many people to Circuit Python, get them interested and provide some of them with hardware to continue at home. After I got home, I got caught up from being gone. I did some PILEAP testing and I closed out a bunch of guide feedback. This week, I will be teaching Liz how to create fritzing objects, sorry, ahead of time. Doing more guide feedback, more PILEAP testing, helping Jeff with getting his library into the bundle and writing a guide page on the differences between MPI, PI and frozen modules for libraries. The initial plan for it was to explain frozen libraries, but after discussion, it actually makes more sense to explain all three of the different setups and how to navigate them and how to use them and what they're for. And that is a point of confusion for a lot of people and a guide page would be excellent. The original purpose was to be able to add a link on CircuitPython.org to a frozen modules page. Well, it'll be a frozen modules section that you can still link directly to. So I will, Neridoc, I will let you know when that guide page is ready to go and you can link to it. And that's what I've got. Thank you. Maker Melissa is up now and then after that, it is time he makes things. Hello. So last week, I attended, I was still at PyCon US 2022 and I helped Katnie with running the open spaces and the development sprints. And I also learned a lot of useful things that will hopefully apply during the next year. And I fixed a couple missing boards on CircuitPython.org. I updated the boot loaders on a bunch of boards on the CircuitPython.org as well. I updated the logging library to now upload to PyPI and updated the Azure IoT library to use logging as a dependency. I tested Blinka on the Raspberry Pi running MicroPython for speed and attempted to optimize, but the changes weren't anything noticeable. So I just ended up closing that issue. I tested and updated e-ink guides to mention that only 24 bit bit maps can be used. And I tested out the 2.13 inch e-ink bonnet and updated the guide for that. And I finally replaced the bulging battery in my laptop. And this week, I am testing, I tested out several pull requests. I may have some more also. And possibly working on a Py portal or actually a matrix portal of requests issues. Possibly working on fixing TouchDriver, so the PyTFT when running the VIP driver. And that's it. Thank you. All right, Scott is on deck, but now it's Tammy makes things. Thanks. So last week I had one Twitch stream. I had a second stream that I was hoping to do that I had to cancel because I was having some back problems that day, unfortunately, but I finished up the core card and deck functionality of my display IO card deck library. So this week, I'm continuing with that and actually getting into the, how do we draw cards on a screen part of the code, figuring out how I want that to work. Hopefully I'm gonna do two Twitch streams. Hopefully also gonna get a chance to do some PR reviews and or some more of the typing hints, PRs and trying to figure out what a regular schedule for working on circuit Python stuff will look like now that I've got a better handle on what my schedule looks like in my new job. And that's what I got. Great, thank you. All right, next is Scott and then I'll round out the section by reading notes from Tectric. All right, hello. Tammy's saying, figuring out new schedule sounds very, very relevant to me or very familiar to me because last six weeks, we had a kid. Baby was born 325, which is a Friday. So it's just over six weeks. So lots of diapers, lots of burping, lots of soothing the baby and lots of love from family and the baby. So this week, still lots of baby time. Becca was out this weekend. So we're, this is the first week. I don't know exactly what the schedule will be. I got like five hours to sleep last night. So brain is not what it used to be. In terms of leave, I will be taking 12 more weeks to leave kind of in mid-August when Becca goes back to work. So you have me for a while. So feel free to ping me. I may not be around but I'll be trying to be responsive and communicate whether I'm around or not and stuff like that. So I'm ramping back up. Let me know what things are high priority for you. I'm not going back through the discord history or the Slack history. I'm going to try to get through the forum and I think email. I'm going to try to just glance through everything. But if there's anything urgent that I may have missed, please just bring it up to me again. And the thing that Lamore is on her radar is the NTP library for Circuit Python is a weird one because it uses something from the ESP32 spy library. Whereas I actually made a version that works with native sockets. So I'll be doing the legwork to actually get that checked in which involves like checking things that use the older functionality of it too. So I'm going to have to run that down and that's kind of the work that I'll start to pick up this week. And in addition to being caught up, I think that's the gist of doing. Sound like I haven't had enough sleep. All right, Scott, we know what you muddle through. Yeah, it'll get better and better and like the kids as they get older, they get more regular schedules and stuff too. So yeah, we'll just get better and better. All right. And to finish things out, I have notes from Tectric. Last week was reviewing Python PRs, working on a script to standardize the pre-commit config.yaml files in the libraries, both content and formatting, adding more links to tutorials, guides, and related reading to the documentation pages for the Circuit Python core modules. Thanks for picking that up, Jeff says. And ordered the PCB for my auto lighting menorah. This week, continuing to refactor the ATECC library, now I have hardware to test, adding more protocols to Circuit Python typing to aid and type libraries, confirming the pre-commit config.yaml script is good to go and then patching the libraries. And maybe it's worth a discussion since it's been recently made available on PyPI. Should adafruit logging be made a true subset of CPython's logging, looking into the differences this week at least. And that finishes up status updates. We're in the weeds, nobody has furnished any topics. And that means that we can wrap up the meeting today. So a big thanks to everybody who was able to join us for the Circuit Python weekly meeting on May 9th, 2022. And I just need to tab back to my other notes to see what else I say. Speaking of people who are totally up to speed and not sleep deprived. So if you wanna support Adafruit and Circuit Python and those of us that work on Circuit Python like Scott and Scott's baby, 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. It will also be featured in the Python for Microcontrollers newsletter. Visit adafruitdaily.com to subscribe. The next meeting will be held Monday as usual at 2 p.m. Eastern, 11 a.m. Pacific. And I believe the date on that will be May 16th, no. Yes, May 16th. The meeting is held on the Adafruit Discord server which you can join anytime 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 Circuit Python Easter's role on Discord. Although adding our calendar is also a great way to just view that within your normal calendar application. Anyway, we hope to see you all next week. So thank you everybody who joined us and everybody who's listening after the fact. Thanks everyone. Thanks.