 Hello everyone. This is the Circuit Python Weekly for May 1st 2023. It's the time of week where we get together to talk about all things Circuit Python. I'm Jebler and I'm sponsored by Adafruit to work on Circuit Python. Circuit Python is a version of Python designed to run on tiny computers called microcontrollers. Circuit Python development is primarily sponsored by Adafruit. So if you want to support Adafruit and Circuit Python, consider purchasing hardware from adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join anytime by going to adafruit.it-discord. We hold this meeting in the Circuit Python Dev Text Channel and the Circuit Python Voice Channel. The 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. To receive these notifications, ask us to add you to the Circuit Python East Discord role. There is a notes document to accompany the meeting and recording. If you're watching it after the fact, the link is in the notes. And we'll include timestamps to go with the videos so you can skip to the part that interests you the most. After each meeting, we post a link for the next meeting's notes to the Circuit Python Dev Channel on the Adafruit Discord. You can find that in the pinned messages and add your notes at any time during the upcoming week. And of course, if you wish to participate but can't attend, don't have a mic or for any reason don't want to speak, you can leave your hug reports and status updates in the document for us to read during the meeting. This meeting is held in five parts. Next up is community news where we take a look at all things Circuit Python and Python on hardware in the community. It's a preview of our Python on microcontrollers newsletter. And I will preview the preview and say this is like a MicroPython heavy newsletter, so much good stuff in there. Anyway, next up after that, we're going to talk about Circuit Python with the state of Circuit Python, the libraries and Blinka. This is a quantitative overview of the entire project, a chance to look at the project by the numbers separate from our status updates. And then third up is the first participatory section called hug reports. Hug reports is an opportunity to highlight the folks, the good things folks are doing, taking the time to recognize the awesome folks in our community. Then status updates, a second round Robin that gives you the opportunity to report on what you've been up to. Take a couple of minutes and talk about what you've done in the last week since the last meeting and what you'll be up to over the next week. And if you don't make it every week, we're happy to hear over a larger period of time, but do keep it to a reasonable length. And then the final part if we need it is called in the weeds. In the weeds is the section where we do any more long form discussions. These can be items that we identify during status updates because a discussion started up or something that you've identified ahead of time that you're sure is too long. And that covers how the meeting will go. Next up is community news. This and more is available in our weekly Python for microcontrollers newsletter, which goes out via email on Tuesday mornings. Visit AdafruitDaily.com to subscribe to the newsletter. Thank you and for putting the newsletter together. If you are out there, anyone in the world, you have Python on hardware news projects to share or find any content that you think is worthy of being included. Please consider contributing it to the newsletter, which we really want to view as a community run effort. You can open a PR on GitHub, tweet at an engineer on Twitter with the hashtag CircuitPython or email cpnewsatadafruit.com with a link. And Ann says it is her pleasure, along with the attendant blood, sweat, and tears. All right. So from the newsletter, here are some of the headlines. Micro Python version 1.20.0 has been released and it contains a wide array of improvements and fixes. More Micro Python news. Check out the links for all the release notes such as that they have Raspberry Pi Pico W support now. Next up, Micro Python is celebrating 10 years. And in the newsletter, there will be a poster the evolution of Micro Python as well as some other visualizations of the development of Micro Python over time. All right. It's not all Micro Python because we released Circuit Python 8.1.0 Beta 2. It is a beta release for a Circuit Python 8.1 and it is now on GitHub and CircuitPython.org. We always value your testing with beta releases. Things are may not be complete. There may be bugs. We need to hear about the bugs so that we can fix them. So check it out and then give us feedback. All right. One project. It is a Micro Python project. It is a traffic light simulation running on the Pimeroni Cosmic Unicorn LED display. One simulates red yellow green lights and one simulates a whole intersection. And there is a Twitter thread as well as full source on GitHub. So I kind of covered this before. But 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. And the place to sign up to receive that in your email box every week is the front page of AdafruitDaily.com. We highlight the latest Python on hardware related news from around the web, including Circuit Python Python and Micro Python developments. And once again, we want you to contribute your own news or project. You can do that in a variety of ways, such as editing the draft on GitHub and submitting a poll request with the changes. You can also tag your tweets or your toots with hashtag Circuit Python or email cpnews at Adafruit.com. And that wraps up the newsletter and brings us to the state of Circuit Python, the libraries and Blinka. And this report contains information from the previous seven days. The report is generated sometime overnight. So any changes today are not included in the report. And of course, because we're generating this based on GitHub API requests, sometimes stuff just gets lost and we really appreciate your contribution even if we fail to acknowledge it here. So overall, we had a large number of poll requests merged 49 from possibly a record 37 authors. So those include Sebastian Falk, Ross K1, Chris Papalardo, a word for that, Pattano, Matland and Julian Clulo, among others. I know that many of these people, I can't even tell us more about it in a bit, were participating with us on the Circuit Python sprints at PyCon this past week. So thank you to all those 37 authors. We also had 10 reviewers who are looking at those poll requests to make sure that they meet our high quality goals and helping people win their poll request isn't quite at that point yet to get things to that point. And there's a name on here I don't recognize KVC0 on GitHub. Thanks for your poll request review, as well as a bunch of the regular people. Issues-wise, we saw 48 closed issues by 13 people and 16 opened by 16 people. So again, a high level of participation. Many of those closed issues were because of those 49 poll requests. So yeah, thank you everybody. And I'm just tremendously excited at what y'all got up to this past week, especially during the Circuit Python sprints. And now Dan has agreed to tell us what is going on in the core of Circuit Python. Okay, thanks. So over the last week, we had 17 poll requests merged. There were 18 authors. Not sure how there are 18 authors and 17 poll requests, but that's all right. And four reviewers and a couple of new ones are Genji Zhao. I didn't recognize Mr. MJ Sir901 and some of the other ones you also mentioned, KVC0. So right now we have 23 open poll requests. Many of these have to do with boards and are drafts and are being, are stuck for one reason or another. Some of them were drafts because they were waiting other work. In the last week, 14 issues were closed by five people and nine opened by nine people. That's nice. There are now 631 open issues. There are no open issues for the 8, for the 8.0 X milestone. So we're not planning any release past 8.05 right now. There are eight open issues for the 8.10 release. There are 26 for 8XX. Things that we kind of like to fix before 9.00. And there are 9.00, there are 26 issues for 9.00. And those are things that need to wait until 9.00 or can wait. Because maybe they're incompatible. There are 21 issues that have to do with libraries. There are 538 issues designated as long term. Eight are designated as support because it's not obvious that they represent a bug. And there are six issues that are kind of stuck because of third party issues. And there are four issues that were not assigned a milestone at the time. This was listed. I just triaged those. So there aren't zero, there are zero right now. And that's it for the core. Oh, yeah. All right, that's it. All right, thanks, Stan. I happen to know about GitHub that there can be multiple authors on one pull request. So for instance, a web late pull request is a great example of that. There's web late itself, which created the pull request. And then there are all the individual people who wrote the translations. And so those are all listed within the notes. So that's how you can have more authors than pull requests. But now I will hand it off to Katnie to talk about the libraries. Hello. Hey. So this section applies to all of the Circuit Python libraries. That's everything in the Circuit Python community bundle, as well as the Adafruit Circuit Python bundle, which is everything that starts with Adafruit underscore Circuit Python underscore and a couple of extras. Across all those repositories, we had 31 pull requests merged by 22 authors. And a number of these folks are brand new. I highlighted them above, so Jeff's already called them out. But we had a lot of engagement at the sprints this year at PyCon 2023. And it's showing through here. We'll put together some actual metrics in probably a week or so because there are still folks working on some of their PRs, which is excellent for multiple reasons. And I want to make sure we include kind of everything that came out of it before we start putting together numbers. We had eight reviewers in terms of the merged pull requests. One, two, three, four, five, six of them were 18 days or older, the oldest one being almost 70, which is excellent. I'm glad we're also getting through older PRs. And we had quite a few that were four, three, two, or one days or zero. We don't put zero days in here. But thanks specifically to, and I have a hug report later for this as well, to Tectric and Foamy Guy, especially Foamy Guy for doing a lot of the reviews on the Sprint PRs. And that leaves us with 63 open pull requests. We had 33 issues closed by 10 people, seven opened by seven people. So we're very much down. And that's definitely coming out of the sprints this year. Leaving us with 595 open issues and 59 of those are good first issues. I believe we were at 70 or 75 or six or maybe. I don't remember exactly, but we were much higher than that. And most of the PRs that came out of the sprints were pulled from that list. If you're interested in contributing to Circuit Python on the Python side of things, check out circuitpython.org slash contributing. You'll find all of this information and more including open pull requests, listed out, and a list of open issues. If you're interested in reviewing, check out the open PRs. If you have the hardware, test it. If you don't, check out the code, see if it looks right to you. If you find any issues, leave a comment and let us know. And once you're comfortable with doing that, we can talk about leveling you up to the review team. If you're interested in contributing code or documentation, check out the open issues. If you're new to everything, good first issue is a great place to start. You can sort by label or you can just do a search and page for a term that may be interesting to you, but find something that you find interesting. Leave a comment that you're working on it. And if you're new to everything, there's a guide written for contributing to Circuit Python using Git and GitHub, which walks you through all the steps. And we're always available on Discord to help you out. You can also request help on the GitHub issue itself. In terms of library PyPI Weekly download stats, this past week, over 310 libraries. We had 100,5845 PyPI downloads and there's a list of the top 10 in the notes. I will note that from the top 10, eight of them are over 1,000 downloads, which is actually kind of unusual. So there's been some excitement, I suppose, happening. And then library updates over the last seven days. We had one new library from Jose David, which is Circuit Python Slider and a number of updated libraries that I will not read off individually. And that's where we are with the libraries. Thank you, Kenny. And I believe you're also reading us the Blinka section today. I am. So Blinka is our Circuit Python compatibility layer for MicroPython, Raspberry Pi, and other single board computers. And over the last week, there was one pull request merged by one author and one reviewer. There are six open pull requests at this time. There was one closed issue by one person and zero open by zero people, leaving 96 open issues. In terms of PyPI downloads in the last week, there were 13,009. PyWheels downloads in the last month were 13,716. And finally, the number of currently supported boards is 101. All right, thank you, Kenny. That wraps up status updates and we are ready to head on to Hug Reports. Hug 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 in the document order to give everybody a chance to participate. If you're text only or are missing the meeting, I'll read your notes when I get to them in the list. All right, so I just want to start off with a group hug. I've been out for about three weeks and I miss you all, but it was also nice to have a break. My PyCon hugs include a huge number of people in no particular order. Kara Willing, Mariata, Ned, who is at Nedbat, Brainwain, Timidrobot and scads of other people I met and talked to, as well as everyone at the sprints and open spaces, especially some additional hugs for Tectric, Keith, the EE, Crayola and of course, Catney for running excellent sprints and open spaces. And finally, Tim LaMoure and PT for funding my attendance at PyCon this year. And then I have some notes from C Grover, who has a group hug to the team and community and a hug report to Tectric for their last poll request. Congratulations. I think we'll be hearing more about that later in the meeting. But next up is Dan. Okay. So thanks again. We get it several times. Thanks to Catney and you and Tectric Crayola and Keith EE for being our presence at PyCon. And thanks to anecdote at Foamy Guy, who've been doing a lot of testing of PRs and issues related to network stuff in the core and various libraries, especially the HTTP server. It really is incredibly helpful to have other people test this stuff thoroughly, saves us time, the core developer's time, instead of having to set everything up to test and other people have more experience with this stuff. And that's very helpful. Okay. All right. Next is DJ Devon three. Hello. Oh, hey, I got Mike working this week. I would like to send a hug to Skir, Mad Bodger, Crazy Guy, S2O, and Xerxes III for all the advice in designing a workshop lamp PCB out of Neopixels. And instead of ordering five 19 inch large ring PCBs, they came up with the idea to split one into 72 degrees, which one times five is 360. So that saved me a lot of money. And that was a really neat project. Well done, everyone for the group effort. That was really cool. A hug to Andy Ward-Burton for helping beta test Wi-Fi, MQTT, and ITC on the UN Feather S2 and S3. Or just the S2, I did the S3. A hug to Dan for helping with mini MQTT error handling issue. It was user error as usual. A hug to Naridoc for helping me figure out how to download a weather gift from NOAA using the Adafruit Request Library. And a hug to Katni, Jepler, Keith, the EE, and Tetrick, and everyone who participated at PyCon this year. Thank you. And next up is Foamy Guy. Hello. All right. It's going, Jeff. Thank you. Echoing what a couple of folks have said, thank you to Katni, Crayola, to you, Jeff, to Tetrick and Keith the EE, as well as anybody else who was out at PyCon representing CircuitPython or even just hanging around and helping the new contributors who popped up. Speaking of, thank you to all of our new or less frequent contributors who made their first contributions or first contribution in a while over PyCon. Had lots of new folks pop in. It's been really amazing to see. Thank you to Tetrick and Jose David for helping review the influx of those PRs. And then lastly, thank you to Michael Pocusa who has submitted a proposal for a new version of HTTP server. This person also put some improvements into HTTP server last week, but there's a new PR open with a new version that has lots of new features that are commonly supported by other platforms, other HTTP servers on other platforms. So it's really cool to see the evolution of that library. And that's what I have for now. Thanks. All righty. Next I have notes from Jose David who writes a hug for Fummy Guy and Tetrick for all the last week PR reviews. And with that, we come to Ketney and then I'll have a bunch of folks to read out notes for. All right. So first up hugs to all the folks I caught up with or met at PyCon. Some of those folks, Marietta, Carol Willing, Chalmer, Tyson, Toshio, Nicholas Tolarvy, Jeff and Ingrid, Alec, Keith and Sarah, Tim and Robot, Russell, Paul, Shauna, Emily and so many more. I needed to write the rest of my hug reports or I would have attempted to list everyone. Special hugs to Jeff, Alec, Keith the EE and Creola for helping out with hosting open spaces and sprints. To Sean Teabor for accepting my education summit talk and helping out during Saturday's open space. To Alec and Rose for helping out with prep before PyCon. To everyone who attended the open spaces and wanted to learn about Circuit Python during PyCon 2023. To everyone who attended the sprints and contributed to the Circuit Python project in so many ways. To the folks who submitted their examples that came out of the open spaces to my PyCon 2023 content repo. I always include an attendee examples folder and I think at least three people submitted the examples that they came up with during the open spaces. To FOMIGuy and TechTrick for all the PR reviews and help provided to our new contributors. I'm not super familiar with type hinting and those were the good first issues that we tagged and folks were really into doing them. But I was not really the person to be able to provide answers to a lot of the questions they had and FOMIGuy especially was available to reply on issues and reply on Discord and help out and keep things running smoothly. To Phil and Lamore for sponsoring me to attend PyCon. To Dave and Mike for bringing me on to the organization team for PyOhio this year and moving forward. To Rose for all her support before and throughout PyCon. To Cgrover and FOMIGuy for adapting and updating their code for my PyCon badge. Specifically Cgrover updated his normal camera code to a much more lightweight version that had only the features I needed so I could have a thermal camera example on it. And to FOMIGuy for the badge code including the ability to connect or to control the NeoPixel LEDs over Wi-Fi and the snake game that was on there and the ability to switch between all three. To the folks who organized PyCon 2023 I can only imagine what goes into such a large conference. The results were a safe space for all a place I felt comfortable with regards to the COVID safety measures and excellent content and I'm looking forward to 2024 in Pittsburgh. To the community and my moderation team for taking such excellent care of our community while I was out. It's utterly amazing and complete relief to be able to step away for any amount of time and know that everything will continue to be the same supportive, positive place as always. And finally a group hug to all the folks I missed. Thank you, Katny. And you mentioned Pittsburgh. They did announce the dates next. The next two years will be in May. It's like already on my calendar. I'll be there. And anyway, I'm getting away ahead of myself. I'm excited. But for now, I've got notes to read from some folks. So Keith, the EE writes, Hug report for Katny, Crayola, Jeff, Tectric for an awesome PyCon. It was wonderful meeting you and it made my first in-person PyCon an absolute delight to Katny for an awesome presentation on the value of the aha moment and for leading the circuit Python events. Those events now have my partner playing with circuit Python. And finally, a hug report for everyone who attended PyCon and joined the community. If you're new here, welcome aboard. And a hug report for everyone. Again, this community is so lovely and fun. Next, hug reports from Makar Melissa. She has a hug for PT and Lady Aida for being very supportive during my move for the past couple of weeks. For Katny, myself, Tectric, Keith, the EE and Crayola for attending PyCon this year. A hug to Katny for reading the Blinka section today and a group hug. Next, notes from Michael Pokusa, who has a hug report for FOMIGY for testing a PR on Adafruit HTTP server that revealed some things that I did not consider or test myself and one for Jay Dimpson for an issue on Adafruit HTTP server related to disabling serving static files. And the last text only in this block is Tammy Makes Things, who writes a hug for Jephler Katny and everyone else who represented the community at PyCon. One to Tectric for his awesome news and a group hug. All right. And now we come to Scott, who I believe will read notes. Yeah, thanks, Jay. First, just echoing what a lot of other people have said, thank you to everyone who put the time and effort into PyCon and making that really seemingly successful. It was very cool to see an influx of people around Sprints. And I know that OpenSpaces, I'm sure, were also awesome. I definitely have a bit of FOMO as somebody who's gone before. So I'll figure it out. I'll go at some point in the future. But thank you. You've done an awesome job. I'm really happy that we had folks there to have a circuit Python presence. So thank you for taking the time and doing the work. And I know FOMIGY wasn't there, but really supporting people on PRs is really helpful, too. So thanks to everybody around PyCon. And then I just had a couple others. So for Retired Wizard and D-Cloud, just thank you to you two for testing the DVI Tweak PR of mine. It's always very nice to have people kind of verify my code because it doesn't always work. And both as D-Cloud and ToddBot gave me feedback on the DVI stuff. And it's going to make it better. So I really appreciate it. All right. Well, taking that feedback in a positive way is really a superpower, too. So good job. All right. And to round out the section, I will read notes from Tectric, who is not present today. Tectric has a hug report for all the fantastic people that I met at PyCon, particularly Katnick Jepler-Crayola and Keith the EE for another incredible PyCon experience. To FOMIGY, who is a David and all the other reviewers helping to get PyCon's print PRs checked and merged. One to my partner for all the love throughout the years, so excited for what's next for us. And finally, rounding out the whole section, a group hug that wraps it up for hug reports. So let me tell you about the next section, which is status updates. It's time to let folks know what we're up to individually. I'll start and we'll go through the list in the document order. 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. This is also an opportunity to provide quick tips and tricks relevant to what folks are working on. But if the discussion becomes long, we will move it down to in the weeds. And with that, I will get started. I've been away for a few weeks, as I mentioned before. I vacationed in Utah, saw some lovely national parks, went on some hikes. Medium hikes can be challenging or they can be just fine. It's interesting. They seem to be defined a little bit differently everywhere. And after that, while in Utah, I figured I might as well attend PyCon. There were so many good things going on in the keynotes, talks, sprints, open spaces and hallway track. And a small writeup of our experience will be in the newsletter. So do check that out. And the totally unexpected thing, I had taken my gel nail kit because I wanted to have perfect blink of purple nails. I mentioned to someone in our, I guess it was Sprint Day in our sprints that I'd be happy to show her how to do gel nails because she was new to it. I brought this stuff down. We went out in the hallway and like when all was said and done, I showed over a half a dozen people. We all sat and did our nails, discussed this and that. I met great people. It's totally unexpected fun. So now I guess we'll do PyCon Polish as an open space in 2024. I hope there are some locals who will bring their stuff because I wouldn't want to bring my nail kit on the plane. And I did get in a little work while I was traveling. I've been working on improvements to Synthio to add ADSR envelope. And I believe that is close to well. So John Park is going to look at that. Maybe Liz will and give me feedback on the API and then it'll go through review and hopefully that will get wrapped up soon. But this week I have received the order to quote, keep Synthen please. So I will get that finalized. I will move next to allowing arbitrary frequencies instead of just MIDI notes and then items beyond that depending on what I get done within the amount of time that makes sense. I'd like to add tremolo and vibrato. I'd like to add a different per note ADSR and waveform. And then kind of the final stretchy stretch would be to add some kind of frequency sweep although based on my experience with changing the note the note qualities, the waveform through just Python code that was running in my main loop that may be enough to do a frequency sweep that sounds good. I also need to dust off my 128 by 32 matrix portal set up put current circuit Python on it and see whether it works. There is a forum user who has reported a problem with it that we failed to diagnose as like a hardware problem. So it's time to test whether the software is still working and I need to check guide feedback and update any guides accordingly and I'm just going to add one more note here in real time that I need to check write channel output on Metro M7 just to make sure that stereo audio out is working when you use that PWM audio out. And my final other is a friend said oh there's an estate sale with cool computer stuff why don't you come and I came home with a Xerox 820 computer system that has a monitor keyboard and two massive 8 inch floppies along with four boxes of floppy disks. The computer itself was widely panned at the time of its introduction as being no better than any other z80 machine not nearly as mind blowing as other Xerox computer products like the Alto but still had an elevated price because of the Xerox name and amazingly it will boot from a floppy and give me a CPM prompt and I'm looking for something useful to do with it. I've got a post on my social about it if somebody cares to paste that into the Discord channel and with that let's hear what Dan is up to. All right. So as people know I released circuit Python 810 beta 2 last Wednesday. I think it was Wednesday, Wednesday or Thursday and on the show on the show and tell I showed the Feather RP2040 prop maker which is a product in progress and had a demo for that. It's a nice all-in-one thing and I've started looking at Greg Nevorov's Async.io rework again now that things are hopefully winding down a tiny bit on 810. So I'll be looking at that and also working on 810 bugs. Okay. Thank you. Next up is DJ Devon 3. Hello. This week I helped Andy Warburton beta test the unexpected maker Feather S2 ran about 25,000 transactions to Adafruit over four days without a single hard fault which should help close multiple bug reports lingering from 7.3.3 all the way up until current stable release 8.0.5 and the UM Feather S2 Wi-Fi is now confirmed to stable along with all of the Adafruit S2 boards. So no hard faults awesome stuff. Also ran the same test on the unexpected maker Feather S3 which might close a couple more issues. So the UM Feather S2 and S3 Wi-Fi, MQT and ITC are all considered stable now and for Scott who likes to keep issues down to one page you can all you Devs can now start looking and closing anything related to UM Feather S2 or S3 Wi-Fi issue. Purchased a Radiolink 189S RC transmitter with a range of about a half a mile. The controller that comes with a little RC sewer tank bot that I'm playing with only has a range of about 20 feet so I will be attempting to swap out the electronics in that for a much greater range. I'm not planning on playing with a two inch tank over a half a mile. It's just so I can get better signal through the pipes sewer pipes. And I just got some new motors in gear reduction 1 to 90 gear reduction to hopefully make a really slow crawler because right now the thing is this fast of a little Ferrari. So that's what I've been playing with this week is mostly beta testing and sewer tank. All right. Thank you. Next up is FulmiGuy. Right. Thanks Jeff. Over the past week or so I've been doing a lot of reviewing and testing the influx of PRs. A lot of the new contributors worked on typing information but there were a few other fixes and improvements sprinkled in in other places as well. It was great to see all of those. I did some more testing for an older PR that was on the WizzNet Ethernet library. Some updates to the internal logic inside of there that I have tested several times and are now ready to go. And that's been merged. So that's another nice one to see get wrapped up. I tried out the proposed new version of the HTTP server. I have in mind to go back and do a few additional examples but I kind of put it through the basic paces so to speak and came away with a good really good feeling about where that's headed. I just I think two or three days ago I got the back and stock notice for the Feather DVI. I got one of those orders so I can get in on some of the HDMI fun once that arrives here in a few more days. Outside of circuit Python world I've been working on a web based application for my wife that will assist in authoring a an HTML file that she writes content for regularly instead of digging through and coding HTML by hand this tool will provide a form within a web page where you can put your information into the form and click generate and it will create all the HTML for you and let you download it. The project uses the flask web framework Genja 2 for templating just the same thing we're using cookie cutter I believe and then a Bulma for the front-end it's been a fun project to work on and hopefully will be helpful to my wife and lastly upcoming for the next week I have in mind to try to expand the HT 16K 33 library to provide a non-blocking text marquee functionality there's currently a marquee in there that will scroll some text for you but it's blocking you can either have it go infinite or just one loop but either way it's blocking and I have in mind a plan to load up a feather tripler or quadrupler with a bunch of different wings and try to get them all interoperating I don't have a specific need for this but I think it sounds kind of fun and the 14 by 4 segments was one of the wings that I grabbed and noticed that it was currently blocking so that's what I've got on my plate for now thanks. Thank you. All right, I have notes from Hasey David who writes reviewed some PRs added the slider library to the community library and worked in the LPS 28 FDW pressure sensor for a circuit Python support. And that brings us back to catney again. Hello again. So I'm back from PyCon it was entirely brilliant and I left home with approximately 70 circuit playground expresses and 30 circuit playground blue fruits and came back with two expresses and about 15 blue fruits which is to say the open spaces were excellent and everyone was super into it. Oddly Saturday was very quiet but evidently the whole conference felt that way Friday was packed and Sunday was even more packed which usually it kind of starts with Friday and then narrows down each day but that's not how it went. We hosted the most successful sprints since we've began hosting them purely based on PR numbers. I'm going to look into getting some metrics put together there so that we have an idea but I want to wait until the folks that are currently working on PRs are also included and merged. I was able to send both the open spaces and sprints folks home with hardware. I had a bunch of feathers and a bunch of different sensors and so during the sprints I asked the folks that were interested what they might want what kind of project they might want to do and sent them home with a feather RP2040 and a sensor that does the thing they're interested in and a STEM acute cable to connect them. There's definitely a few things that could be approved upon for next year but nothing serious it was all small things that would make the experience smoother for the folks involved. I created a list. It's basically updating the quick start stuff we had to highlight the more important stuff on the page for example or having better signage for the doors stuff like that. But overall it was probably the best we've ever done and I definitely feel like we've kind of got the process nailed down at this point. It's just a matter of tweaking the small things. I was able to see a lot of friends that I haven't seen some since 2019. I was able to meet a bunch of new folks. That was excellent and in terms of circuit Python I'm just amazed at how many people were were interested in learning about it. I ran a small workshop at the Education Summit before the conference itself and had the Education Summit was not super highly attended and I probably had 15 16 people who decided to work with me over like a couple other options. So that was kind of cool. Separately I am jumping into joining the organization team for Pi Ohio this year in a big way with specific role details still to come but I'm super excited for this week now that I'm back to work. The next thing on my list is finishing up the RFM 95 RP 2040 guide got that started before I left and have that to to finish up now. The Metro M7 guide needs details on the PwO on my page about which pins actually work for PwO my oh or audio or I have better notes somewhere else but there's something about specific pins. I'm going to be doing a guide on a canary nightlight which if you are familiar with they might be giants it's came about I had birdhouse in your soul stuck in my head so I'm a little excited about this as well and I need to write up the code for it Noah already modeled the 3d printed bird and it looks amazing. I have four guide updates to do some of them small some of them a little bit bigger but those will be happening between other things and then sometime soon I will be discussing details with Tetric on updating the CI on the GitHub repository that contains all of the code to shorten up the time and resources currently used by every PR at the moment it builds everything every time and it does catch things at times so we came up with a solution that both shortens individual PR times and still will catch the overall stuff that changes in terms of mostly Arduino stuff will sometimes like a library or something will change out from under us and so that will fail on a specific example totally unrelated to the PR so we will be handling that as well and if you have any questions and want more information about Python feel free to ask there I could go on for ages but I won't um and just know that it was excellent and um I'm really glad that everyone was able to join us and glad that I was able to attend and that's what I've got all right thank you all right I've notes from a couple folks so maker Melissa writes for the last two weeks got the code for a collaboration project with Erin in a good place and successfully finished a big move from Oregon to Las Vegas I worked on packing loading and driving with between 12 and 18 hour days for a solid week and a half or so this week will be catching up on email messages issues and guide feedback adding some additional changes to the co-lab project based on feedback and lots of unpacking getting services hooked up and finding things next up is notes from Tammy makes things who writes last week completed the first round of design for a project I'm building for my nephew an audio amplifier and oscillator board which combined with a tiny oscilloscope from Amazon will enable him to make a map of sounds this week prototyping and testing the different sub modules of my map of sounds project before I do the board design note if there's anyone who's good with analog circuits and wouldn't mind looking over my schematic for obvious mistakes please PM me I'd appreciate another set of eyes and of course there is the help with channel for circuit board design but anyway and finally Tammy's note last note for this week is hopefully working on the design for an rp 20 40 build I'm designing to be base for music slash MIDI projects and other under the heading of other still struggling with health stuff health stuff but hopefully getting closer to a successful resolution and that brings us back to ten new again okay I've got a number of kind of things that are close number of PRs that are close I've got a PR out for supporting the I am X R T 10 15 10 40 and 10 50 in circuit Python and I also have a tiny you have to review as well for that I've got a couple library PRs for e-paper fixes for little Indian addressing they're waiting on reviews as well Melissa hey I pinged you on those so hopefully you see those in your email I am waiting on a review from you Jeff on a PR not by me but that I took over for frequency setting on the rp 20 40 and I have a PR out that I just had a Dan as a reviewer on for switching pico dvi frame buffer to taking the frame buffer size and not the signal output size I don't know if I talked about this but is like the six used to always be 640 by 40 or 4800 by 480 and if you gave it color it would automatically divide it down now with if you give it color depth 8 or 16 you've got you've got to provide the smaller 320 by 240 or 400 by 240 and and hope that it allocates do it early if you want to try to get to allocate so as I'm wrapping this stuff up I'm going to circle circle back I started a learn guide about porting the circuit Python API to a new board and and although the gotchas and chat like kind of basic test programs that to run through that so I'm going to circle back with that once all of my pending stuff is kind of done on my side I'm I'm going to probably start to by making a list of what modules I'm going to cover to complete it because there is kind of a long tail of stuff but I haven't done bus IO yet so I'm going to have to do that and so that's kind of what I'm going to dive back into this week and that's been kind of centered around verifying that I am XRT port is kind of working as we wanted to and getting it to the stable point so that's it for me all right and to round out the section of status updates I have some notes from rights last week reviewing PRs from Picon so excited to see all the issues closed this week with more in the works and a second item that I'll just read exactly what it says here in the the working notes document there's a photo that won't make it to the final notes document so take a look now after nearly four years of collaborative effort I am excited to announce that my most extensive pull request was recently accepted maintainers are now discussing when the changes will be merged but are thrilled with your additions and there's a photograph of two people in there so you can decide what that means for yourself and anyway tech drink this week catching up on things post Picon some new ideas for fixes and patches emerged during and since so I'll be looking into those and that wraps up status updates thank you everyone and there are no topics for in the weeds today which this has been the circuit python weekly for May 1st 2023 thank you to everyone who participated if you want to support Adafruit and circuit python and those of us that work on circuit python consider purchasing hardware from the Adafruit shop at Adafruit dot com and if you're outside the U.S. there is a link to our official distributors at the bottom of the page the video of this meeting will be released on you too at your podcast services it will also be featured in the python for microcontrollers newsletter you can visit Adafruit daily dot com to subscribe the next meeting will be held next Monday as usual at 2 p.m. Eastern 11 a.m. Pacific that will be on May 8th the meeting is held on the Adafruit discord which you can join by going to A.D.A. F.R.U. dot I.T. slash discord to be notified about to be added to the circuit python easter's role on discord it's free that's the only thing that we mention you about and there is no obligation although we'd also love for you to come participate in the meetings and with that all I can see all I can say is I hope to see y'all next week thank you everybody thanks everyone