 Hello everyone. This is the Circuit Python Weekly Meeting for April 25th, 2022. It's the time of week when we get together to talk about all things Circuit Python. I'm Jeff, and I'm sponsored by Adafruit to work on Circuit Python, which, as you may know, is a version of Python designed to run on tiny little computers called microcontrollers. Circuit Python development is primarily sponsored by Adafruit, so if you want to support them and Circuit Python, consider purchasing your hardware from Adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join any time by going to adafruit.it.discord. We hold this meeting in the Circuit Python Dev Text Channel and the Circuit Python Voice Channel. This meeting typically happens on Mondays at 2 p.m. Eastern Time, 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 preferred calendar app. We also send notifications about upcoming meetings via Discord. If you'd like to receive these notifications, ask us to add you to the Circuit Python Easter Discord role. There is also a notes document to accompany the meeting and recording. The notes document, when you read it after the fact, contains time stamps, so you can use it to skip to only the parts of the video or podcast that interests you most. The meeting tends to run 60 to 90 minutes, so we think it's handy for you to have the option to skip around. 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. You can check the pin messages to find the latest note stock and add your notes any time during the week before the next meeting. If you wish to participate but cannot attend, or if you don't have a mic or for any reason prefer not to have your voice recorded, you can leave hug reports and status updates in the document and we will read it out during the meeting for you. So this meeting is held in five parts. Next up is community news where I'm going to take a little snapshot of the Circuit Python and Python on hardware notes from the upcoming Python on microcontrollers newsletter. After that, we head to the state of Circuit Python, the libraries, and Blinka. Go to getting a statistical overview of the whole project, a chance to look at the project by the numbers separate from what we're individually up to. Then comes the participatory part. In hug reports, we offer the opportunity for anyone to highlight the good things that folks are doing, and we take the time to recognize the awesome folks in our community. Then we turn to status updates. Status updates is an opportunity to sync up on what we're all up to. Take a couple of minutes and talk about what you've been doing in the last week, since the last meeting, and what you will be working on up till the next meeting. And we also love to hear other little tidbits of what is going on in your life. So please don't hold back if you have news about how it was 90 degrees on Thursday and then froze on Friday like it did here. Crazy stuff like that in the weather. May have been Saturday, I forget which day. Anyway, and then the last part, which we don't hold every time, but based on need is called in the weeds. It's an opportunity for a more long form discussion of anything pertaining to Circuit Python or the community. And we invite you to add those topics as soon as you become aware of them, either throughout the week or during status updates, just whenever it becomes clear, the sooner you put that in the document, the better. And while the first two interactive sessions are alphabetical order, that one is first come first serve. And that covers how the meeting will go. So I am going to switch over to the other document and head to community news. So first up, and this is a big one for me, PyCon US 2022 is this week. The event is in person with an online component from April 27th through May 5th in Salt Lake City, Utah. There is a website which for me guys kindly getting the links to. Thank you for details about the conference and the schedule. So Katni, Melissa and I will be attending. They will be there from April 28th through May 3rd, including the Education Summit where Katni will be giving a talk called Simplicity and Fun Learning with Circuit Python. Then during the main portion of the event, we will be hosting a Welcome to Circuit Python mini sprint within the open spaces component. No, I guess the Welcome to Circuit Python mini spread is also during the pre-conference, my mistake. Then next up is the open spaces every day during the main conference where we will do a introduction to Circuit Python using the Circuit Playground Blue Fruit. The Blue Fruit boards will be provided along with a few accessories to enable folks to explore Circuit Python. A quick start will be available as well as a series of other examples to delve into. And the three of us will be coming and going from those and Katni has put together a great little kind of two-page curriculum for people to learn from. Then I head home, but Katni and Melissa continue through the sprints on May 2nd and 3rd, which is a great way to kind of get embedded in the development of Circuit Python, primarily through the libraries. But we really invite you to show up and just figure out how you fit in. And yeah, I'm looking forward to hopefully meeting at least a couple of new people. So yeah, check out that blog post to find out a little bit more about what we're up to and keep your eye on the Adafruit blog to find the time of the open spaces or look at the signage within the conference. Anyway, that was a mouthful. Next up, we have some software from around the web. Microbit has created a Python editor and that has reached beta status. And so the Microbit Educational Foundation is excited to announce that our new Python editor has entered its beta phase, meaning we are getting ready to release it to the community. And there are links to the mailing list and the support sub-site. And I'll read a quote. The new editor has been built from the ground up with classroom use in mind. It aims to make text-based coding more accessible to students who may find it hard to engage with the subject by removing known barriers to learning. It's also designed to make computer science appeal to more diverse cohorts and hence expand their horizons. And I believe that's working with the MicroPython port for Microbit. And then Tom's Hardware did a review of the Pimeroni Servo 2040. And I'm just going to read a little bit about it here. There is a link. We tested the Servo 2040 using MicroPython and CircaPython. Pimeroni has created a new version of its MicroPython release, which provides support for the Servo 2040. And it seems that roboticist and developer Chris Parrott has poured a lot of love into the software that supports this project. And it is also backed by great documentation. And I'll talk a little bit more about the Servo 2040 later when it comes to what I've been working on. Next up, more online or more IDEs intended for classroom. The CircaPython online IDE has released its four classes edition. It is nearly the same online IDE as the existing CircaPython online IDE. However, in this project, teaching functions are provided. And just what those are, you can find out the full text in the newsletter. The CircaPython Weekly newsletter, which this has been a preview of, is a community-run newsletter emailed every Tuesday. The complete archives are at adafruitdaily.com. It highlights the latest Python on hardware-related news from around the web, including CircaPython, Python, and MicroPython development. To contribute your own news or project, edit next week's draft on GitHub and submit a pull request with the changes, the links are in the notes document. You can also tag a tweet with hashtag CircaPython on Twitter or email cpnews at adafruit.com. And there's a whole huge fraction of the newsletter, which is People's Projects, which I always love. But there was so much of kind of the headline stuff that I didn't even get down to them today. So go sign up for the newsletter at adafruitdaily.com if you're not on it already. And check out those projects. I just love seeing them every week that I run the meeting. I get so excited by what's in there. But that wraps it up. Just a hat tip to Ann. Thanks for keeping the wheels on this thing and making a great newsletter every week. So that brings us to the state of CircaPython, the libraries, and BlinkUp. And I'm going to give you an overall kind of pulse and then hand it off to some others to get a little more specific. So overall, we had 30 pull requests merged from 20 authors. There are some names that are new to me or don't show up a whole often. And I will just kind of go through a few of them now. I apologize because I'm going to print on some of these wrong. Anyway, Stone Hippo, Zhu Hao, Bill Van Luen, 424, Mark Singh TW, and Urun Syaband are some names I didn't recognize. And also, NerdCornet, I think may also be another new or newer contributor. So thank you to all 20 of those authors, most of whom are outside of Adafruit. So if you're able to help us make the software work better for everybody, we really appreciate that and we couldn't do it without you. Reviewer-wise, we had six reviewers and thanks to all those folks and thanks to people who also just comment on pull requests and on issues and help us find the information that we need so that we can resolve the problem or implement an improvement, whether you're formally recognized as a reviewer or not. And finally, issues-wise, we were on a real downtrend with 25 closed issues by 11 people while we had just nine issues opened by seven people. And I asked Dan earlier if he would update us on what's going on in the core of CircuitPython. So go ahead, Dan. Okay, thank you, Jeff. Okay, in the past, since the last meeting, we've had 14 pull requests merged by 13 authors and there were three reviewers. Scott is out on paternity leave. So Jeff and I are doing a lot of the reviewing and thank you, Gambler21, for doing some reviewing also. There are 17 open pull requests. Some of these are drafts and are in process. There aren't too many that are really stalled, which is good. There were seven closed issues by four people and three opened by two people, so we did have a small net improvement. That's great. There are 523 open issues. And of those 523, there are 7-2.x milestone, has zero open issues. Unless there's some new showstopper issue that comes up, we probably will not issue another 7-2x release. There are nine open issues that we hope to fix for 7-3-0 final release. There were 29 issues we hope to fix by the end of the seven series. There are 12 issues open for 8, which those are all deferred until 8 happens usually because they're incompatibilities of some kind between major versions. We've got 19 open issues that pertain to libraries and we've got 455 long-term issues which are things that we might get to there, suggestions or enhancements and sometimes bugs. And there's one open issue on support and we have negative two issues. Maybe that's an imaginary, maybe it's really minus 2i issues, the imaginary issue is not assigned a milestone. So that's it for the core. All right, thank you, Dan. No releases in the last week or so, right? That's right. I might make a beta sometime this week, but just a catnip. All right, and next, Katnie, I just assume that you are all ready to tell us about the libraries. I am. Great. This section applies to all of the Adafruit Circuit Python libraries, which is everything that starts with Adafruit underscore CircuitPython underscore, as well as a couple of extras such as the community bundle and our cookie cutter. So across all of those repos, we had 16 pull requests merged from nine different authors and five different reviewers. Most of the merged PRs was over a month old, so I'm glad to see we're still getting through some older PRs. That leaves us with 26 open pull requests. We had 18 issues closed by eight people and six opened by six people, leaving us with 629 open issues. 198 of those are good first issues. If you are interested in contributing to CircuitPython on the Python side of things, check out circuitpython.org slash contributing. You'll find all of this information and more, including pull requests, open issues, and library infrastructure issues. With the issues, if you're looking to contribute documentation or code, check out the issue list. Good First Issue is a great place to start if you're new to everything. And we have a guide on contributing to CircuitPython using Git and GitHub, so don't let that part intimidate you. We're also always available on Discord to answer questions. If you're interested in reviewing, check out the open PRs and if you don't, take a look at syntax spelling that sort of thing and leave a comment. Let us know you looked at it. That's super helpful. And once you're comfortable with that, we can talk about adding you to our review team. In terms of library updates in the last seven days, we have no new libraries, but we have a short list of updated libraries that I will not read, but they are in the notes. And a quick thing, I guess, that's kind of fun to look at. And then we also have a look at Adafruit Discord badge. I pointed to Discord already, but now we have a little custom badge that says Adafruit Discord and has a little star on it. I'm kind of excited about that. And that's what I've got. Thank you, Katnie. And to round out this section, I will invite maker Melissa to give us the Blinka updates. Hello. We're at MicroPython, RatsprayPy, and other single board computers so that the CircuitPython libraries can run on those boards. And this past week, we had zero pull requests merged. There are currently four open pull requests. There were zero closed issues by zero people and zero open by zero people, so no activity, leaving a net of 74 open issues. There were 11,172 PyWheels downloads last month, and we are currently supporting 88 boards. And that's it. And it's not directly going to show up in the numbers on Blinka, but you're working on some pretty exciting stuff with the displays on Raspberry Pi, right? Yes, it's called Getting Frustrated about writing device tree overlays. All right. More about that in status updates. Thanks, Melissa. No problem. Next, we come to hug reports. So this is the first of our two round robin sections. And let me just jump to my blurb that I'm going to read out. Hug reports is a chance to highlight folks in the CircuitPython community and beyond for doing awesome things. As mentioned, this section is held as a round robin, where I will start and then we'll go down the list alphabetically. If you're text only or missing the meeting, but have hug reports in the notes document, I'll read those off as I get to your position in the list. So, my hug report is first to Lady Aida for always having excellent quests to Dan for pinging me when I dropped the ball on an mp3 problem, which I didn't put in status updates, but I'll try and remember to talk about it. Ketney for doing a bunch of behind the scenes a bunch of behind the scenes work to prep for PyCon. And lastly, Scott, hey, I hope you're doing well. I hope you're doing an excellent job of not being seen well on Paternity Leave. And next up is C Grover, who is just listening in today and has a hug report for Fome Guy and Naradok for insightful revision control advice as I began a long delayed quest into Get More Door. Today's release of Fome Guy's How to Make Pull Requests to Contribute Video was particularly timely and helpful. I'm seeking secretly longing to return to the Shire, however. And with that, it is Dan, who's up next. Okay, thanks. So I'd like to thank Kurtie and MJS 513 who are continuing to work on a lot of fixes for the TNC boards, the I.MX boards. Some of these are specific to TNC and some of them are more general to the NXP I.MX family. So thank you for that. Thanks to Tetrick, who's been doing a bunch of documentation and typing fixes, both in the core and in libraries. And thanks to you, Jeff, for improvements to RP2040PIO in a variety of ways, making it more and more useful. Okay. Alright, great. Next I have notes from David Cloud and up after that is Fome Guy. So David writes, I've been following in the recordings without contributing to the weekly meeting for months, so group hug because there are too many things to celebrate, such as Liz joining Adafruit, Scott's family extension, Tim for deep dive, and an ellipsis. Alright. Over to you, Fome Guy, and then to Jerry. Alright, thanks, Jeff. Hug reports this week. Thank you to NeerDoc. NeerDoc shared a really cool user interface, like web-based user interface that you can run in the browser for circuit python packaging. Kind of like pulling all the libraries and stuff. Sort of like circuit, but a visual way to see it, which is a really neat project. Thank you to Tammy Makes Things for the streams on Twitch, working on circuit python and python development, and then a group hug for everybody else. Thanks. Alright. Jerry, go ahead and then Katnie after that. Hi. Thanks to NeerDoc for being very patiently explaining to me how to access the micro bit LED matrix on Discord this morning. After Katnie will be Kmatch, but go ahead, Katnie. Alright. This week I have a hug for Eva for running an adabot patch to update the library.getignore files to match. And running a script to update the chat badge on the libraries to the new Adafruit Discord badge to Fome Guy for updating the URL used for the Adafruit Discord badge to the raw URL. So Read the Docs also rendered it properly. To Jeff for writing a script to automatically load circuit python and flash a directory full of content onto CircuitPy to save me a bunch of time. To Rose for modifying said script to be fancier because that's how she works. And to Brian and Rose, Brian being my housemate for joining the flash party to get CircuitPython and content loaded onto 90 circuit player on blue fruits in preparation for open spaces at Python 2022. To Rose for helping in general with PyCon Prep and a group hug. Alright, thank you. Makeumlessa is on deck, but now Kmatch, what is up? Thanks, Jeff. Got one hug this week. This is to GitHub user Suda Morris who I believe is probably on the expressive development team. Thanks to them and I guess the rest of the team for backporting some fixes to the RGB LCD library. Back into the version 4.4 of the ESP IDF which will make it a little bit easier to get it into CircuitPython. So thanks, Suda Morris. Thanks. Alright. After Melissa is Tammy, but go ahead now Melissa. I wanted to give a hug to GitHub user Bad Seafood for contributing a well-written device tree overlay last year that's working as a great reference to Catney for the hard work prepping for PyCon and group hug to everyone else. Go ahead, Tammy, and then I have one set of notes to read. Wait, just a second for Tammy to come back. Sorry about that, I hit the wrong button. Happens to all of us. I just have a group hug for everybody this week. Alright, thank you. And to round out the section, Tektrick writes a hug for Naradok for the fix regarding the edit GitHub link on the CircuitPython API docs. A hug to Catney for all the neat things that will be at PyCon, excited to swing by and check it out. And finally, a group hug. So that finishes hug reports and we will move on to status updates. Status updates is our time to sync up on what we're doing. This section is also held as a round robin. When I call on you, 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. And where it's relevant this is a great time to provide tips and tricks as long as they're quick. If it is a longer topic that doesn't really fit within status updates please add a topic to in the weeds. And anyway, I will start. So last week yet again, I'm trying to put the finishing touches on floppies. I still have a little bit left. It has to do with how you count track numbers on all different kinds of floppy drives. It's a little bit dry but needs to get finished. After Dan pinged me a second time, I worked with a user on the Adafruit forums to find a new problem with mp3d coding, which we believe will be fixed. There's emerged PR and it should be in 730. And then late in the week, I started on a quest to improve the state machine to let it use that new servo2040 board from Pimeroni to its full potential. And basically, at Pimeroni, they had invented a very cool way to use one PIO state machine to create up to 32 different PWM outputs. And there was something missing so you couldn't directly adapt that code into CircuitPython. And I've added the missing piece and kind of done a prototype of the code that you would actually use to control the servos that this is in a couple of pull requests on GitHub for more. Anyway, this week, it's just two and a half days of normal work this week that I'm heading to PyCon, as previously mentioned. So I'm trying to fix those items that I just mentioned above and I started investigating whether to do a rewrite of Adafruit PIO ASM with a goal to fix some, it accepts some programs that it shouldn't and this tripped me up and I lost some time on it last week but also these changes might allow us to add calculating the values of expressions which is in the standard PIO assembler from Raspberry Pi but doesn't work in CircuitPython. So it's gotten to the point where it handles about four, three or four instructions and it's already a larger program than the original. So I'm not sure if the size will be an issue but I'm going to continue playing with that and it will be an easy thing to do while at PyCon if I have some downtime I'm going to write code. So that's what I'm going to be up to and so I'm going to read notes from Cgrover in just a moment and then after that it's Dan again. So Cgrover writes I learned enough to get revision control concepts to successfully submit an NAU 7802 driver class to the CircuitPython community bundle. Congratulations. In conjunction with a custom featherwing design the driver reads sensitive analog load cells for various scale and torque converter projects. And Cgrover is working on submitting three more driver classes and a collection of helpers to the community bundle. This is not only a good educational experience but also an opportunity to fine tune some older code with my evolving skill set. As a visual and experiential learner I'm hoping to codify and document this into a set of process flow diagrams that I can reference from my occasional use in the future. And if you do I hope you share those with the community because people have all sorts of different ways that they feel most comfortable learning and help us enable more people to work on CircuitPython. Anyway, Dan you're up and then I'll read notes from David. Okay, thanks. So I've been working for some time on ESP32-S2 I2C problems. When you run at Hertz there's a big gap between each I2C transaction which makes for instance controlling a stepper motor through an I2C controller really slow because the steps there are many steps and if there's a 10 milliseconds delay on each one that just makes the stepper run really slow. So I did a lot of work inside ESPIDF and sort of found an empirical fix which involves inserting a slight delay some time and place. I brought this up with I opened an issue about this in the ESPIDF repo and the official maintainer of I2C stuff looked at it and found a different bug which fixes an example that I wrote but doesn't fix it in CircuitPython. So I'm not quite sure what to do at the moment but I'm waiting for that maintainer to submit a fix to the other repo and I'll try it again. And there are also a lot of other I2C fixes going on in ESPIDF. So it's kind of a mess right now. That brings up the second point which is there's an ESP32S3 I2C issue which is also in process in the ESPIDF repo and I'm looking at that. And then finally I have all kinds of NeoPixel strips lying on my desk because I've been doing a lot of testing of NeoPixel timing and NeoPixel like things are made by different manufacturers and some of them require slightly different or not slightly different quite different timing so I've been trying to make sure that the timing we have works with everything that we sell and I'm just about there but the timings are quite different than what they used to be so I'm working on that and then hopefully everything will work on everything with the Python eventually. It seems that some of the common wisdom about NeoPixel driving is not entirely accurate based on our internal discussions so that's always fun to learn. Anyway after I read notes from David I will hand the talking stick to FomeGuy so David writes last week converting we you draw game tablet to absolute mouse HID for PC as seen on show and tell and there is a link to twitter in the notes doc also mouse emulation using custom standalone USB HID descriptor rather than using the built in composite descriptor my proof of conference proof of proof of concept demonstrates how to use a we you draw tablet with the Nintendo switch and their current project is emulating a mouse to automate texture drawing on the game builder garage a switch game that allows you to create your own games alright FomeGuy we are ready for you and then after that it will be Kenny alright thanks Jeff this week I created a sprite button class that allows you to make buttons display IO based buttons with any arbitrary bitmap that you want so we can have some fancy your buttons now I made a PR for that in the display button library but it was previously just a single file so I also refactored it to be a package and then Pilant complained about some of the code being copied so I also made a base class to try to put all the common stuff in the base class and then the subclasses now have their separate behaviors is one of the things that I worked on that kind of went into that button was this tile grid which I have made a PR for now over in image load this basically allows you to take a relatively small 3 by 3 sprite sheet and then inflate it up to a bigger size tile grid so the button is based on that and I have a couple other widgets that are in the works that will use that as well I as was mentioned earlier I made a couple automation scripts to update the URL in the read me file for the discord badge due to some differences in the way that github and read the docs are able to render images essentially earlier today I published a YouTube video that demonstrates how to make PRs for circuit python libraries going into this week a couple of the things I have on my list are looking back into making a little draft notification badge or something like that on the contributing page on circuit python.org for the PRs so it will draw something to signify which ones are draft PRs and which ones are just plain open ready for review I think I have figured out where that data comes from and I have also figured out the template where it gets rendered into the page and I just need to get my adabot environment set up so that I can actually start tweaking the data that is in there another thing I want to do this week is work on some touch interaction in the tab layout. I started making the tab layout I think a week or two ago and it's also kind of based on this tile grid inflator so it was one of the first things I used that for but I need to go back and do the touch interaction for it and then get the code cleaned up and get ready to make PR for that and then the last thing I have that I know of so far at least is got a couple PRs that I'm going to be testing out later this afternoon one of them is a sharp display stuff which I haven't set up or used before so I'm excited to kind of play with a new type of display to test out some of that stuff. That's what I got. Thank you. Next up is Ketny and after that is Kmatch. Alright so last week I published the Feather ESP32S3 guide and jumped into testing PyLeap which is an app that allows you to transfer projects project code to either a Circuit Playground Bluefruit or a Clue or the boards that are supported at the moment with it just plugged into power so not plugged into your computer. It works on iOS. Anyway a little background there but tested all the projects to make sure they load both on Clue and Circuit Playground Bluefruit Trevor is our iOS dev I worked with him to get the bugs to get bugs fixed and then tested the bug fixes and I added a new project to PyLeap using the new process which is submitting the project via a JSON file that is kept on GitHub and PyLeap just picks up that new project and that's used to be you had to go in to learn and enable it and that sort of thing and it was not very public friendly because we want folks to be able to add to this who are not necessarily in the Adafruit Learn system so I tested that out as well and it worked as expected and PyCon Prep so this week I need to finish testing PyLeap there is a new test flight with the latest updates so I need to test that I need to get through as much as possible before leaving for PyCon which is easy and difficult test flights the release cycle on those is sort of under Apple's control so you can't just make a test flight and have it immediately show up it could be anywhere from 1 to 24 hours so I won't be able to test a new version of it this week I don't think but I can make sure that the bugs that I filed have been addressed or at least added to the upcoming test flight and then more PyCon Prep and then on Wednesday I leave for PyCon giving a talk at the Education Summit before the conference I'm running a mini sprint at the Education Summit I'm hosting open spaces daily I say me, we are hosting open spaces daily during the conference and then Melissa and I are hosting two days of development sprints after the conference this past weekend was a lot of PyCon Prep including flashing circuit python on content onto 90 circuit playground blue fruits counting out and packaging up 80 usb micro cables because I realized we can't expect folks to have those anymore because most technology does not use usb micro it's usb-c or lightning obviously so whereas previously we could expect folks to have those cables we can't really do that this year since blue fruit is micro and that's what we'll be working with I wanted to have cables available and a bunch of other smaller things that happened there's still a lot left to do but I got a couple days to do it so it would be good to go and looking forward to seeing anybody who is going to PyCon look for us, look for our open spaces come by and say hi and I guess that's what I've got thank you that's a lot as per usual alright Kmatch and then maker Melissa thanks Jeff not too much progress this week due to some house projects that materialized and worked as well the main thing I'm doing is trying to prepare my thoughts for a feature request into the expressive IDF in particular related to the RGB LCD display based on circuit pythons allocation of all the psoram in advance basically I need a function of their init function to be able to accept a pre-allocated frame buffer so I just want to make sure that works like I think it should and propose how that might work so that's the main thing this week but nothing else planned until other things settle down thank you so after making Melissa we will have Tammy and then some notes to read so go ahead Melissa okay last week I was working on a script to install the new MiPi driver and figuring out all the offsets and the rotations especially for the ST7789 display this week I I mean the next item I did was I worked on a device tree overlay for a touchscreen driver for the STMPE touchscreen controllers and I didn't quite get that working yet I think I'm actually really close and I started working on a device tree overlay for the TSC 2007 and this week I'm going to try and wrap up the touch screen device tree overlays and do a little bit of Picon prep and then I'll be heading out and going to Picon later and so I'll be attending and also working with Katnue on her talk workshop in open spaces and looking forward to meeting you Jeff thank you alright then Tammy it looks like you've got a good list of stuff going on what's up so last week I only did one twitch stream I was hoping to do two but I just started a new job and so things have been a little bit that would be a nice word for that and so this week I'm hoping to do two or maybe even three twitch streams I'm still working on my circuit python card deck library and now that we're seeing more and more boards that have lots of flash I'm hoping to get back to my fix for the new tool so that it works properly on those boards that's what I'm hoping on getting done today or this week I'm also expecting significant FOMO around not being a Picon but hopefully next year so we'll see how that goes and that's what I got alright thank you and to finish out the session I will read the notes from Tectric last week mostly packing up my things and moving them to a new apartment so it was a light week addressing some long-term documentation issues in the core thank you adding more typing protocols to circuit python typing to aid in a few type annotations for libraries and a few random bug fixes this week is Picon 2022 and unboxing the things I just boxed and finally probably a few type annotations during the flight and downtime and that concludes the status updates next up would be in the weeds but we don't have any topics so I will move to wrapping up the meeting so this has been the circuit python weekly for April 25th 2022 our next meeting is at the usual time on Monday May 2nd at 11am pacific 2pm eastern time so we hope to see you there although I will be missing it so yeah thank you to everybody who participated today and thank you to everybody who listened in we really appreciate that you are interested in what we are up to to support aid of fruit and circuit python and those of us that work on circuit python consider purchasing from the shop at aidofruit.com the video of this meeting goes on youtube at youtube.com slash aid of fruit and we also put the podcast on most major podcast services it will also be featured in the python for microcontrollers newsletter visit aidofruitdaily.com to subscribe um this meeting is held on the aid of fruit discord which you can join at any time by going to adafru.it slash discord we have people in just about every continent and time zone so come by talk to us about your projects and then join us on Mondays for the meeting um to be notified about the meeting and the changes to the time or day you can ask to be added to the circuit python east's role on discord which is also a must when you want to participate in the meeting by speaking in the voice channel alright I think that really wraps it up uh hope we'll see most of y'all next week thanks again everybody thanks everyone