 Hello, everyone. My name is Tim, and this is the Circuit Python weekly meeting for December the 12th, 2022. This is the time of week where we get together to talk about all things Circuit Python. Again, my name is Tim. I'm sponsored by Adafruit to work on Circuit Python. Circuit Python is a version of Python that's designed to run on tiny computers called microcontrollers. The development of Circuit Python 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.com. We hold a meeting in the Circuit Python Dev text channel as well as the Circuit Python voice channel. This meeting typically happens on Mondays at 2 p.m. Eastern time, 11 a.m. Pacific time, except when that coincides with the U.S. holiday. In the notes document, there's a link to a calendar that you can view online or add to your favorite calendar app. We'll also send notifications about the upcoming meetings via Discord, so if you'd like to receive those notifications, you can ask us to add you to that Circuit Pythonistas Discord role. I'll mention it again at the wrap-up, but just a heads up. Next week's meeting is normal time and date, and then the following week, I believe, is the week we are off, and then the one after that is when we have the change to the Tuesday, just like this was saying, for the U.S. holiday. Upcoming scheduling, if you need reminders, take a look at that calendar linked in the docs. Speaking of the doc, the notes document to a company, excuse me, there is a notes document that a company is the meeting. This is a Google doc. This is pinned in the Discord channel if you need to get access to it. The notes document contains time stamps that go along with the video, so you can use the document to view only the parts of the video that interest you most. The meeting tends to run 45-60 minutes, so this gives you the option to skip around. After each meeting, we post a link to the next meeting's notes document in the Circuit Python Dev channel over there on the Adafruit Discord. Check the pinned messages to always find the latest notes doc, and you can always add your notes to that throughout the week as well. Once that gets pinned, the new one is created following the meeting, you can of course add your notes for next week, starting whenever that's up. Go ahead and do that throughout the week if you like. The meeting structure, the meeting is going to be held in five parts. The first part is going to be community news. This is going to be a look at all things Circuit Python and Python on hardware in the community. The preview of the Python on microcontrollers newsletter. The second part is the state of Circuit Python, the libraries, and Blinka. This is a statistical overview of the entire project. It's a chance to look at the project by the numbers, separate from what we're all up to. The third part and the first of our two round robins is the hug reports section. Hug reports is an opportunity to highlight the good things folks are doing. Take some time to recognize folks in our community and beyond for good stuff that you have seen them do. The fourth part and the second of our two round robins is the status updates section. During status updates, this is an opportunity to sync up on what you've been up to for the week. Take a couple of minutes, tell us about what you've been doing since the last meeting for the last week and what you plan on doing for the next week until the next meeting. The fifth part and final part of the meeting is in the weeds. In the weeds is an opportunity for more long form discussions. These discussions can come out of status updates or they can be stuff identified ahead of time as too long or in depth for status updates. So if you've got topics for in the weeds, go ahead and scroll down to the bottom of that dock and get those added just as soon as you come up with them. And then we'll go over whatever topics are there to close out the meeting. So that covers how the meeting will go. So first up, we are going to look at community news. So let me get there and get a timestamp for us. And first in community news this week is the Circuit Python 8.0.0 beta 5 was released. So beta 5 has been released. It's relatively stable, but there will be further additions, fixes and changes before the final release. There are links here to the Adafruit blog as well as GitHub if you would like to check out the release notes or anything else related to that new release. Please do, if you have projects and things that run Circuit Python, please do try out the new release if you have a chance and let us know over on Discord or in issues or somewhere on GitHub if you have trouble with any particular project. And of course, thanks to the folks who will try that out for us. And an early hard report thanks to Dan for making the new release. Next up in community news, we've got a video interview with Guido van Rossum. This is titled Python and the Future of Programming. A recent interview by Lex Friedman, Guido van Rossum, Python and the Future of Programming. And there is a link here to watch that interview over on YouTube. So check that out if that sounds interesting to you. Next up is a Korg synthesizer that uses a Raspberry Pi. This is the Wave State synthesizer. Korg created this device and showed it. It's a spiritual successor to the legendary Wave Station synthesizer from 1990. This device was first on display at NAMM last month. According to information from sonicstate.com, the WT hardware, Wave State hardware, is based on a Raspberry Pi. And there is a video that's linked here in the dock as well as the newsletter for this week that shows somebody taking apart one of these devices. And indeed, it does look like a Raspberry compute module is in there. So that's definitely super cool to see that. Next up in community news still, this is tutorial pages on the Adafruit learn system or user pages, I should say. So a relatively recent feature added to the Adafruit learn system is the ability to create user pages. This is a new way to add your own content for make this allows you to use the same technology that are in the Adafruit learning system to publish your own tutorials and guides on the internet. This week highlighted in the newsletter are some user pages created by community member Joey Castillo. And in particular, it is a NeoPixel powered Christmas tree that has an Adafruit LCD feather wing. There's an implementation of a one button UI for scrolling it to turn on and off. And it uses the circuit pythons deep sleep feature to save as much power as possible when the tree is in the off state. And there are links here to Macedon as well as those user pages on the learn site. And then two more items in community news to round it out. These are a couple projects from the week, a couple things that caught my eye. The first one is a bit of a wacky keyboard, which I'm always kind of a sucker for. This is titled the ultimate Unicode input device. It has 18 physical switches, which you can flip on and off, which represent 18 bytes of binary and then a single send button. So you flip your switches to indicate ones and zeros for a, you know, a binary representation of a Unicode character, and then you press your button to actually send it to the computer. So I thought that was really funny, interesting thing. There's links there to a different blog as well as Hackaday. And there are videos of that in action, if that's the kind of thing that you find amusing like I do. And the last one this week, which I also couldn't bring myself to not put in here was a barcode clock using the Pimeroni Badger 2040 that runs with MicroPython. So this is a fast updating E-ink display. And this person who has posted information about this to Twitter has created a clock, which simply just cycles through the seconds of the day. But the nifty part about this is it also displays the time as a barcode. So if you scan the barcode at any given second, it will tell you what time of the day it is. So this is kind of interesting to watch the time tick by and see how it affects the barcode. So lots of great stuff. All of these items and many more came from the newsletter, which I will timestamp for that as well and then tell you about. This is all from the CircuitPython weekly newsletter. It's a community run newsletter that's emailed every Tuesday. The complete archives are available on AdafruitDaily.com. It highlights the latest in Python on hardware related news from around the web, including CircuitPython, Python, and MicroPython developments. To contribute your news or projects, you can either edit next week's draft on GitHub, submit a pull request with your changes. You can also tag a tweet with hashtag CircuitPython on Twitter or email to cpnews at Adafruit.com. And of course, thank you to our very own Anne B for collecting all of these great things for us to look through each week in the newsletter. That gets us to the end of community news. And next up, it will be the state of CircuitPython, the libraries and Blinka. Let me get to the right spot in my dock here. So this is a quantitative overview of the entire project. It's going to give us a chance to look at the health of the project separate from what we're all up to. We'll talk about the project overall and then separately discuss the core, the libraries, and Blinka. So first up, I will tell you about the overall stats for this week. This week across all CircuitPython projects, we had 23 pull requests merged from 17 authors. A couple of the authors whose names I don't recognize as being frequent contributors, perhaps these folks are newer or less frequent contributors, or perhaps I could just be mistaken, but those names this week that stood out to me were S-OL, Evil Dave 666, Pontus O, Boran Roni, Cassane Ho, Boolean Matak, and Vladak. Those were the names again of folks that might be newer or less frequent contributors, so thank you to them. And of course, thank you to all the rest of our more regular contributors as well. For those 23 pull requests, there were seven reviewers in there, so those do look like all the usual suspects, so thanks of course to our normal reviewers, members of the team here. Appreciate all of those folks as usual. We had in issues, there were 18 issues closed by nine people with 18 opened by 14 people, so net even on issues, but they are churning. We're getting opens and closes to keep stuff moving, so this is all good. Next up, I will hand it over to Scott to tell us about the core, if that's all right, Scott? Sure. Thanks for running the meeting, Tim. And I scrolled right by it. For the core, we had 16 pull requests merged from 13 different authors, so thank you to all of our authors. Boolean Matak, Pontus O, our Boran Roni are look like new names to me, so thank you to those folks. We had three reviewers, so we're always looking for more reviewers. We have 19 open pull requests and drafts are now marked, so thank you. I believe Tectric did that. If I'm wrong, please correct me. So we have 19 open pull requests, eight are drafts, so we have 11 open that are non-drafts, which is pretty good. And the oldest two are about 300 days old, so we should take a look at those and figure out what to do about them. Issues-wise, for the core, we had 13 closed issues by five people and 11 opened by 10 people, so again, we're kind of, oh, Dan marked the drafts by hand, this time at least. So thank you to all of the folks that are involved in issues. We have a total of 578 open. We categorize those to prioritize for the Adafruit-funded folks that work on Circuit Python, and we have zero open issues for 73x, which means 73 is pretty good. And we have 13 open issues on 8.0, which is significantly down from the 20 plus that we had last week, so that's been really good in making lots of progress on 8.0, which is good and helped to have it out in January. And then we have 508 open long-term issues as well. Three don't have a milestone, so those are the ones that we will need to take a look at and categorize, so that's it for the core. Excellent, thanks Scott. And next up will be the section covering the libraries. Ordinarily, this section is read by Katny, but she was unable to join us today, so I'll read the libraries section. So this section covers all libraries, which are hosted on GitHub under the name of Adafruit underscore CircuitPython underscore, and then there will be a library name following that. These are all the Python layer of code that allows Circuit Python to interact with various different pieces of hardware, sensors, and things of that nature. This week in library land, we had seven pull requests merged by five authors, a couple of those same names that I mentioned before look like newer contributors on the library side of things. And then for those seven pull requests, we had six reviewers this week, and again those do look like the usual suspects. So thank you to all of our authors and reviewers for the week. Other stats in library land we do have, I should say, 42 pull requests that are open. Over the week, we had five closed issues by four people with six opened issues by four people. There are currently 589 open issues of those 97 are marked as good first issues. And to go along with that, I will mention if you're interested in getting involved with development, the libraries is one of the best, most easiest places where you can do that. There is a website dedicated to that if you go to circuitpython.org. There's all sorts of information there about how to contribute and what kinds of things you can start working on if you do want to contribute. If you're interested in this information and more, check out that page at circuitpython.org. You'll find all the open PRs as well as open issues and a list of library infrastructure issues. If you're looking to contribute, that's a great place to start. The issues can be sorted by label, so you can search for good first issue if you're just getting started, or if you are a bit beyond the basic steps, you can also filter those on bug or enhancement. If you need help, there is a guide for contributing with Git and GitHub. We're always happy to help folks that want to get started. If you do need help beyond what is in the guide, you can always join us on Discord and ask for help there. There's plenty of folks who are always willing to help folks contribute. If that is something that you think you'd like to do, please do get involved. We're definitely happy to always see new folks coming on board. That is it for the library section. Next up is the section covering Blinka. I don't see Melissa in there, so I'll read the Blinka section. Let me get scrolled. We do have the PIPIs. I already passed it up. I'll do my timestamp and do Blinka. We'll do the PIPI stats next week for the libraries. I forgot those. That one's on me. For Blinka this week, though, we did have no action in Blinka Land. Zero poor requests merged by zero authors and zero reviewers. There are 10 open poor requests, including a couple newer looks like a few of those are about 10 days or so old in terms of the Blinka PRs. Across all the Blinka issues, there were zero issues closed by zero people for the week and one new issue opened by a single person. There are 87 current issues open across Blinka. The PIPI downloads for the last week for Blinka are 22,598, and then the Pi Wheels downloads for the last month are 7,327. There are 100 boards currently supported by Blinka. We just crossed the 100 board milestone for Blinka, so that's very exciting. That brings us to the end of the status report section, which gets us to the first of our two round robins, the hug reports section. Hug reports, to reiterate, this is a chance for folks to highlight members of the Circle Python community and beyond for doing awesome things. I'll start and then we'll go down the list alphabetically or as names appear in the notes document. We'll give everyone a chance to participate. Your text only or missing the meeting, but you have some hug reports. Go ahead and note those in the document and I'll read them as we get to your turn in the list. I will start out this week with hug reports. Let me get a timestamp here. My hug reports for this week. Thank you to C Grover, who published some helpful color utilities in the community bundle a while back, and shared some example code that uses those to create some interesting gradients this weekend in the Discord, as well as showing how to integrate those with vector IO shapes. I think there's lots of interesting stuff possible based on some of these examples that C Grover has shared as well as the utilities that they made. So thanks for that. Also hug reports this week. Thank you to Dan Jeff and anybody else putting hard work into the get EMV effort. Definitely really appreciate all the effort that's going into that. I think that's a really good move forward for us with accessing secret variables. So thanks to all the folks working on that. And then last one for me this week is a group hug. So next up, I will pass it over to C Grover. If you want to tell us your hug reports. Yeah. First, I'd like to thank Katny and UFO me guy for recommending pie charm. I was kind of a stubborn converter from Adam. And since they pulled the rug out from under us, then I had to move to pie charm. But the documentation for the setup and usage really made a big difference. And it took me about a week to get used to pie charm. But I've seen improvements in my workflow already. So thank you for that. I'd like to recognize DJ Devon for some of the innovative work that he's been doing and openly discussing and documenting it. He's doing some pretty cool stuff. And I like looking at his innovation and the artistic approach that he's taking. Again, to foamy guy for thought provoking sessions. The stream to build gradient color fills for display IO shapes helped me to break some log jams in my concepts for the approach I was taking on the pallet slice wrapper project. So thanks. So it's great to hear. Thanks C Grover. Next up, I will pass it over to Dan. Okay, thank you. So over the weekend, we started seeing a continuous integration problem on GitHub actions, which was kind of confusing. And I'd like to thank micro dev and Jeff for working on this really weekend or at least taking a look at it and micro dev proposed several fixes for it as well. It was hard to understand. Thanks to Jeff, who's been working on OS dot get in kind of over and over again, revising it some of the time because I brought up some ideas. So thanks for your patience with my suggestions. And thanks to catney. The GitHub security issue came up and we had to deal with it and catney and I kind of split up the responsibility for that. So thanks to catney for that. Okay. All right. Thanks, Dan. Next up is DJ Devon three who's text only. So I'll read their hug reports. Following that actually is D glad who's text only as well, which I'll read in the next one. If you want to get ready will be Jeff, you'll be after these two that I read. So back to DJ Devon three first though, hug reports from DJ Devon to catney for an excellent Macedon API guide. Hug report for Liz for hosting show and tell for her awesome vlog on and for her awesome vlog on modular MIDI music melody maker. Hug report for foamy guy me for teaching new things every week. The learning never stops. And then last one from DJ Devon three is a hug report for Jeff for excellent chat GPT demo in circuit Python on last week's show and tell next up is David cloud. Let me get a timestamp who is text only and has a group hug for everybody. And now I will pass it over to you, Jeff. Hello, where's that other mute button? I have a group hug and I want to thank Dan for patiently working through the giddy and V changes with me. I guess we're both being super patient with each other during this time. It's been a bit of a slog, but we'll get it done soon. And that's what I have. Thank you. All righty. Thanks, Jeff. Next up is catney who is missing the meeting today. Catney has a hug for maker Melissa for helping with a really difficult pin outs page in an upcoming product guide helped looks like Melissa helped out with initial info went over it and made further edits as needed to make it solid. Hug report again from catney. This one's to Liz for being a great partner in crime or maybe not crime but learning and for always being able to answer questions and for me to bounce ideas and things off of a hug reports. Well, catney mentions as always, I'm certain that I'm forgetting folks. So of course thanks to anybody who may have been forgotten not listed here and they group hug for everyone. So thanks to catney for those. And next up is Scott. Hello. First a hug report to micro dev for helping me get the ULP going. I had basically like given up on getting it working and then micro dev gave me an example that worked and I figured out what my problems were with my example. So thanks to micro dev for giving me that little push and getting me over the hump on getting the ULP going. I think it's a kind of a neat thing. So I'm kind of excited about it. ULP is short for the ultra low power processor on the ESP32 S2 and S3 chips. There's also one on the ESP32 but it's not a risk five core which is more interesting to me. Thanks to Jeff Blur for tommolifying the environment settings and hug report to anecdote for further NDNS testing. I know that I've been kind of ignoring all that stuff but I do appreciate anecdote of really living on the edge and pushing it to its limits and documenting where it falls over. So that's it for me. All righty. Thanks Scott. Next up in rounding out the hug reports is TechTrick who's text only. So I'll read. This week TechTrick has hug report for Paul Cutler for having TechTrick on the Circuit Python show talking about continuous integration and CircuitPythonica project and a second thanks for letting me record letting me re-record part of the podcast for accuracy and then a group hug. So thanks to TechTrick for those and do be sure I don't think it was mentioned anywhere else but do be sure to check out that version of the podcast which was released I think even earlier today perhaps with TechTrick on there. So that rounds out the hug reports. Next up will be the status updates. So as a reminder status updates is our time to sync up on what we're doing. Take a few moments to tell us what you've been working on since the last week, last week's meeting and what you'll be working on until next week's meeting. This is a good opportunity to provide tips and tricks relevant to what people are working on if a discussion does become too much or too long we can always move it down to in the weeds section. So this is another one of the round robin sections I'll begin and then we'll just go down the list as the names appear in the notes doc which should be mostly alphabetical but we'll just follow the doc even if it's not quite. So first up my status updates for the week. I last week worked on MPY building a specific branch from a library PR which requires a couple of tools to be set up and running I didn't have those in my new environment yet so I kind of got myself back up and running to be able to build those MPR files excuse me MPY files. Specifically I was attempting to test a PR for the Ethernet library there was something in there that I think I had seen in the past maybe behave differently in MPY so I wanted to make sure to test it in a actual compiled one rather than just the Python one so I got that all set up and did the testing last week. Last week I also implemented the set root group functionality inside of Blinka display IO so this is a recent API change in the core and I have now put out the PR to update Blinka to behave the same as the core now does and then the other stuff that I was getting into last week is a bit of learning about color theory and adapting some CPython code that I found that generates gradients to work with CircuitPython and display IO. There were both linear and poly linear gradients on the page that I found both of those are implemented and working in CircuitPython I just put them in a basic bitmap for now but I think there are other interesting ways you can make use of them once you've got your palette generated. The last one which was in that resource was called a bezier curve gradient and so I want to work on implementing that one this week and converting it over to CircuitPython so that we can use it and then put some time into figuring out the best way to share what I've come up with. I think it's display IO is kind of the primary thing that I'm intending to use it with but I think possibly it could have other uses like maybe neopixels or other situations where you could be outputting color so fun stuff going on there all the way around and then I don't necessarily know what I'll be getting into beyond that for the week so that's all I've got this week on status updates so next up I will send it over to Cgrover. Well let's see I've been working on a palette slice wrapper class that I talked about last week a little bit that's the a class that will take a display IO palette and treat it more like a list so that you can do inserts and deal with things like slice objects so that you can manipulate the palette just like you would with a list so this week's progress was including transparency content along with the color content so the next thing to do with that though would be to look at some of the functionality that may be needed to make it look even more like a list for append and insert and extend in some of those extra functions so I'm about ready to make the alpha repo public but I want to do some additional tests so I won't be embarrassed when I release that anyway I'll post a link to a demo that shows the an image that was that has a palette of about 256 colors and no transparency but it runs through a bunch of random slices of it and gives a pretty good example of how well it works and then I've got a side project that I'm working on out in the workshop to duplicate a broken wind chime that we have and it's something that was in my wife's family for quite a few years and it's something that is it makes a lot of noise in the neighborhood so we certainly want to get it back up on the back porch you make it stronger going to make it brighter than it was in terms of the colors and materials but the best part is going to be selecting the tune that it's going to play and so I was thinking about classical music or something in a major key and I think we may use something in a minor key just to scare the squirrels away something like that a friend of mine suggested that we tune it to play happy birthday but I think there may be a city ordinance against that thank you thank you see grover sounds like a quite the interesting project for sure next up is dan okay thank you all right so last wednesday I released circuit python 800 beta 5 which had like more than 80 call requests in it I'm going to do try to do beta 6 quite soon because it'll have the incompatible that changes we're changing dot end to a kind of a restricted subset of toml to be settings dot toml for various reasons including that it's really hard to create files that begin with dot on a couple of different operating systems and also to make the syntax be a little more a little more like python in terms of quoting and things like that meanwhile I've been just working on a to a bug fixes I investigated some bugs some are no longer problems so I just closed them some were pushed I pushed a xx or later because they don't need to be fixed for 80 or can't be fixed for 80 I fixed a couple of minor ones and I've got some other ones in the works working on some things and also awaiting hearing from the original posters we are now down to 13 issues as was mentioned earlier which is terrific that really looks a lot more like the light of the end of the tunnel compared with the 30 that we had a few weeks ago so I also besides fixing those bugs I've been reviewing other folks PRs making some suggestions on those and I wrote up an issue that we're having with a continuous integration as I mentioned in hug reports I didn't fix it but Rocker Dev and Jeff are working on fixing it okay thanks thank you Dan yeah next up is DJ Devon who's text only so I'll read um DJ Devon says showed off the cutie pie parent BFF on show and tell it's a great little grounding board for le g led projects found some more problems with the tr cowbell and beta testing uh yeah and beta testing shipments are going to be delayed from that uh stemma qt port doesn't work so not going to bother soldering the connector to the boards um DJ Devon did confirm that itc works there's a workaround for using itc on pins 10 and 11 only which is not what they had in mind when designing it um got an ender s3 excuse me ender 3 s1 pro 3d printer DJ Devon got 3d printer going this week started designing an orange cap for the eta fruit step switches uh took seven iterations before getting one that fits and works right not thinking about designing my own step switches from scratch that are more like the original tr 808 switches uh the step switch model I got from CAD parts doesn't have functional doesn't have a functional switch mechanism specifically it's miss missing the center nub that presses the switch uh so be aware that it's a cosmic cosmetic only 3d file floating around for excuse me which is fine for adding to pc pcb designs for a 3d view uh but not for 3d printing of course if you're expecting to actually be able to use it um redesigning it into a working version that's not just cosmetic uh hoping to pr the working stl file in eta fruits cad parts uh github this week the first thing I've ever designed for a 3d printer this was the first thing I've ever designed for a 3d printer so cool uh DJ Devon getting involved in uh some 3d modeling this week for the first time uh and then the uh there is a picture of the component if anybody's interested in the image of that 3d model uh and then the last bullet point here for um status updates for DJ Devon says switching back and forth between learning fusion 360 3d printing and designing the modular tr cowbell version 1.3 using smd components it's been a busy week all right next up is uh david gload I believe I said that right but if not I apologize and I'll have to have you remind me but I know you told us a couple of weeks back so hopefully I got that one right uh david this week says uh for this week gave a gemma m0 mouse jiggler to a co-worker uh maybe they'll try to adapt it uh to circuit python code uh installed circuit python on my new lowland boards the c3 mini versions 1 and 2.1 the s2 mini the s3 and the s2 pico uh which has got a 128 by 32 OLED display uh testing some new accessories uh 32 by 64 OLED uh proposing a PR to add support for 32 by 64 OLED inside the display i o ssd 1306 library and there's a link to a PR there uh making a lego dumb terminal for the 32 by 64 screen and there's a link to an issue there um which I will definitely check out later I'm getting interested in lego so that seems kind of cool to me uh for next week david says uh try to apply eta fruit 5 by 5 neopixel grid bff learn guide to the eight by eight rgb shield uh to scroll text like liz and jeff have done um try to apply the bluetooth tv zapper learn guide to an ir control shield uh need to build the ir translator to let my google tv remote turn off my beamer all right uh and then next up is jeff so i will send it over to him hello again so last week i finished the guide for the next keyboard which is published in the eta fruit learning system we took a 10 year old guide done for arduino on a very classic keyboard and rewrote it for circuit python and that was a lot of fun i continued the work on os.gid env which has turned into a bit of a slog i think we're seeing the light at the end of the tunnel keep you posted i papered over a poorly understood pico w bug by adding an extra one second delay at startup i don't have a board that exhibits this problem neither does dan so we went with a delay that we knew was safe and would get these folks running again and i fixed a bug that could cost crashes at soft reset time on expressive boards by shutting down ssl sockets in a well-defined manner uh this week number one is definitely getting the os.gid env wrapped up and then catney and i will work through how to upgrade a guide that was using the dot env and then we will hand that off to eva to get the guides that have been published thus far updated and then after that i will get back to the other 800 blocking bugs i've not picked out the next bug uh in personal stuff our 18 year old super's head gasket is failing it's been our single car since our good car was totaled in 2021 uh somebody hit it while driving recklessly down the street hit our car and totaled it that was fun uh and then found out that the car that we'd like which is a Prius has at least a six month wait um so we're on a waiting list at our local dealership hopefully we don't end up a zero car family it's not super easy in this city but we're not 100 sure what we're going to do in the meantime and that's what's up with me right thanks jeff i got my fingers crossed over here on the car situation for you next up is catney who was unable to make the meeting today so i'll read catney says last week put the i spy guide into moderation started the event countdown timer guide which is a collaboration with noe and liz this week catney says finish up the countdown timer guide add a new board definition with a board dot button for the latest revision of the feather rp 2040 and if this gets finished up uh next will be miscellaneous or other guide from the list or both so thank you to catney for sharing some notes in here and then next up is paul cutler who's missing the meeting so i'll read paul says new episode of the circuit python show is out today with tech trick uh who shares how circuit python uses continuing integration and his circuit pythonica project uh and then next up is scott hello um so in terms of when i'm around i'm out on wednesday to travel we're flying back to michigan where my wife's family is um and then i'm working four more days thursday friday monday tuesday and then the 21st which is next wednesday i'll be taking off through the new year i might try to do well if i have time i might do some other stuff but no promises um and then i'll be back on the third with the meeting and uh i'll work for michigan tuesday wednesday thursday and then we travel on friday the sixth so that's kind of my holiday plans um before i go before i stop working my goal is to wrap up this espu op testing and the the api that i did it's a rework of the coprock api that was already added um i'm pretty interested and excited about it i've got some tooling now where you take a c a main dot c file and it produces kind of a self-contained python file that like loads the code for you and and does all that stuff which is pretty neat um so i want to get the pr baseline for stuff that for that stuff in and that's blocking 8.0 because that's an api change um and then i'm going to port that tooling uh refine the tooling for the ulp but i also want to reuse some of that for the stem of g0 that i have which is a kind of a stem coprocessor thing as well um for the testing for the ulp i need to make sure that deep sleep is not broken with it um deep sleep on the s3 is currently broken because of the ulp just being enabled even if though it's not used i gotta figure out why that is um so that's my main goal and then two other random things one is if you are using web workflow on the esp um last week i fixed some responsiveness responsiveness issues it was like pretty slow and kind of frustrating and then i fixed the issue and it was like much nicer to use so that's that was great that happened uh early last week um and then on the personal side i have a backup computer here that has like lots of hard drives in it with data and i was upgrading it to um a new Ryzen thing because i had a spare motherboard and that it's not coming up and it's been really frustrating um it like powers on sometimes and i thought the memory was bad because it powered up without the memory in but then i like went to plug in a usb drive with you know some linux on it so that i could get it working and it completely shut down and now it doesn't power on again um and i ordered like a new power supply for it so it's going to power supply um so that's been frustrating and i don't have time to fix it before i go on vacation so it's just going to sit here yeah computers i know right it's fun but always work yeah yeah like if any if folks have systems they use that just do it for you now might be the time that i'm most amenable to it so if you have suggestions for how to back up data locally and like remotely do another place uh let me know all right all right thanks scott um next up and i believe yep rounding out our status updates section is tectric who's text only this week so i'll read tectric says last week began some backlogged improvements and fixes for adabot adding draft pr status to the pr is listed announcing updates to the community bundle patching fix for the bundle creation ci appears to be failing for the community bundle worked on updates to the composite actions used by the library ci those updates to that composite actions were updating versions of actions like set up python to current versions addressing deprecation warnings for steps in the ci will bring those fixes to blinka and the core as needed um tectric also mentions mysteriously still doing okay with the advent of code and c it's pointers all the way down and then for next next week tectric says beginning to wind down as my grad course comes to an end with the final and as excuse me to an end with the final and the holidays approach please feel free to tag me if the ci breaks and i'll be happy to spring back and fix it working to close out relevant open prs and leave it in a working state before disconnecting later this month beginning to make up my excuse me circuit pythonicas everything has arrived on time going to build them and ship so that they can arrive before the holiday and that gets us to the end of the status updates section so our fifth and final section for this meeting is the in the weeds section in the weeds is an opportunity for more long form discussions that either come out of status updates or were identified ahead of time as too long for status updates if you've gotten in the weeds topic please make sure they get added to the notes document um there is one here so if anybody has another one in mind please go ahead and add that while we're talking about the first one um the first one that we do have is from uh micro dev uh i don't see micro dev in the voice channel so i'll read this one out but of course folks can follow along with this in the note stock as well so uh mic oh it didn't read far enough ahead it says missing meeting right there so micro dev says um they would like to discuss uh this issue i'll link that in the chat here as well uh this is an issue on the core four five five four four five five four is the issue uh issue number yep uh it was a suggestion to add count on alarm as a replacement for count i o um it looks like the open question maybe is how kind of filling in um based on shorthand but i think the question is how should the api work only adding count i o dot counter which takes an alarm object is option one add count i o counter alarm and move sleep functions to sleep dot light sleep uh in sleep dot deep sleep so option two was that one adding the counter and then moving the sleep functions and then option c that's listed is add alarm dot count on alarm that takes an alarm uh and i will really admit i don't do much with the deep sleep so i definitely don't have any thoughts on that does anybody else have thoughts or ideas around this issue well he didn't suggest alarm dot count alarm so you know right now alarm has pin alarm and time alarm in it so i'm not sure i don't think i wouldn't replace count i o with an alarm because there are plenty of uses for it that don't alarm you involve alarming people do use it to count things i think i think it's i think we'll just follow up on this issue i'd like to know more details about what they're trying to do and i suspect that actually the ulp could be enough like if you need something to wake up and increment something uh like the ulp might be just fine nice um i mean they they obviously know that because micro dev added the first version so uh yeah i would just say like i looked at the issue and it's it doesn't have a concrete example in my mind so i'd like i'll just follow up there okay okay wait for some more and for there all right um and that was our only item for in the weeds no new ones have appeared so i will assume nobody has anything else um which gets us to the very very last part the wrap up which i will read over here so this has been the circuit python weekly meeting for december the 12th thank you to everyone who participated uh if you want to help support adafruit and circuit python and those of us that work on circuit python please consider purchasing hardware from the adafruit shop at adafruit.com uh as a reminder the video this meeting will get released on youtube at youtube.com slash adafruit the podcast will be made available on major podcast services uh it will also be featured in the python for microcontrollers newsletter visit adafruitdaily.com to subscribe to that uh the as i mentioned before the next meeting next week's meeting on the 19th is at the normal time 2 p.m eastern 11 a.m pacific on monday uh the following week however this is your your early warning for that the following week is the week we're off and then the week following that is uh when it gets moved to the tuesday so we've got a couple of changed meetings upcoming after next week which will be at the normal time on the 19th um so keep that in mind get that in your calendar if you need this meeting has been held on the adafruit discord which you can join by going to adafruit.it slash discord um if you want to get notified about the meetings please ask to be added to the circuit python easter's roll uh we'll ping that roll whenever the meeting does change and those notifications will still come for those upcoming meetings as well that i mentioned so thank you to everyone again who participated that's going to be it for now thanks everyone and have a good week