 Alright, I have my time stamper going. Hello everyone. This is the Circuit Python Weekly for March 27th 2023. This is the time of the week when we get together to talk about all things regarding Circuit Python. I'm Dan 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 at any time by going to adafru.it.discord. We hold the meeting in the Circuit Python Dev Text Channel and the Circuit Python Voice Channel. This meeting typically happens on Mondays at 2 p.m. U.S. Eastern time at 11 a.m. U.S. Pacific time, except when it coincides with the U.S. holiday. In the notes doc, there's a link to a calendar you can view online or add to your favorite calendar app. You also send notifications about upcoming meetings via Discord. If you would like to receive these meetings, ask us to add you to the Circuit Python Easter's Discord role. There's a Google Doc's notes document to accompany the meeting and recording. The final notes document includes timestamps to go along with the video so you can use the doc to skip around and view the parts of the video that interest you most. The meeting tends to run 45 to 60 minutes. After each meeting, we post the link for the next meeting's notes document to the Circuit Python Dev Channel on the Adafruit Discord. Check the pinned messages to find in that channel, to find the latest doc notes doc so you can add your notes for the following meeting. If you wish to participate, but cannot attend, you can leave hungry ports and status updates in the document for us to read during the meeting. We hold the meeting in five parts. I'll go over them as we get to them. Okay, so I will start with community news and this is a selection of stuff from the Circuit Python, the Python for microcontrollers newsletter that comes out tomorrow. So first up, let me put a timestamp in. Oops, okay. All right. First up, there are 100 Circuit Python community libraries. The Circuit Python community reached a big milestone together. Now there are 100 libraries in the Circuit Python community bundled. Circuit Python libraries are separate files designed to work with Circuit Python code. So I want to distinguish between the community bundle which contains libraries supported by members of the community and the Adafruit Circuit Python library bundle which contains libraries that are supported by Adafruit. We really appreciate the community bundle and the fact that it's so large now. As Adafruit, we can't support all these libraries. Some of them are special purpose or pertain to products that we don't make and we really appreciate everyone who works on the libraries in the community bundle. You can find out what's in the bundle by going to circuitpython.org slash libraries and looking at the bundles there and their pointers to what's in the various bundles. And then the next thing up is right here in the Discord community, we've reached 37,000 members which is sort of unimaginably large and keeps growing like about 10 a day. So we really appreciate everyone who's joined. Adafruit believes that Discord offers a unique way for Python on hardware for folks to connect. It's really been very successful. So I mentioned that these newsletters, these items come from the Circuit Python Weekly newsletter. You can contribute to this newsletter by opening a poll request on GitHub. There are notes, there are pointers in the notes document for how to do that or you could send email to cpnews at adafruit.com or you can tag us with hashtag Circuit Python on Twitter. Any of those ways are great for getting news to us that to go as proposals for things to go in the newsletter. I really appreciate it. We all appreciate it. Okay, next up is the state of Circuit Python, the libraries and Blinka. This is like a quantitative overview of the entire project with all kinds of numbers about how many things have happened. It gives us a chance to look at the health of the project separate from our status updates. We'll talk about the project overall and then separately discuss the Circuit Python core, the libraries and Blinka. So first overall, in the past week we had 45 poll requests merged by 18 authors. A couple of new ones, Azgur Boston, is representing an organization that from Turkey that has contributed several new boards. Saintis is new and those are the people I recognize as new. There may be others. There were eight reviewers of those 45 poll requests and there were 26 issues closed by 10 people and 12 opened by 12 people. And now let's go on to the core specifically and Jeff will do that for us. Hello, apparently my mic was open already. Sorry about that. Anyway, so the core is the part of Circuit Python that is written in C and it's based on MicroPython and it's kind of where all the low level stuff goes. And last week we had 33 poll requests merged, which seems like just a huge number from 15 authors, including those two that Dan was talking about earlier and five reviewers. Thanks particularly to Liz with CityDIY as well as MicroDev1 for doing those reviews. We'll find it very helpful and it lets us land better tested changes in the core. In terms of poll requests, we have 20 open poll requests of which about eight are not marked draft and those range from one day to 404 days old, 191 for the ones that aren't drafts. So if you're able to work on a draft PR that you opened, please do so. If it is out of date or you're not going to get to it, please feel free to close it and then reopen a fresh one at any time. And if you are waiting on something from us, please let us know so that we can help get all those changes into the Circuit Python core. Issues-wise, we saw 17 closed issues by six people and four open by four people, which is a very nice decrease. And this represents mostly the hard work of our poll request authors, although in some cases they may be closed because they were out of date or were support issues or other things like that. Anyway, that leaves us with 629 open issues, which we usually focus on using GitHub's milestones. Milestones show how Adafruit is prioritizing work on Circuit Python, although if you want to contribute to Circuit Python, you should feel free to work on whatever interests you. For 8.0x, we have zero open issues, which means that as far as we know, 8.0x is a really stable release that is serving people's needs well. And if we hear about bugs in version 8, then we will add them to that milestone. Otherwise, we're looking at 8.10, kind of the next feature release of Circuit Python, and we'd like to resolve 11 open issues before we release that. And meanwhile, for smaller items, we tagged those with 8xx, and we've got a larger number, 70 open issues in that category. And finally, looking ahead to the next kind of breaking release for version 9, we have 21 open issues. And long term, those issues where Adafruit's not prioritizing them, but community, we welcome your work on it. We've got 500 of those issues. We've also got issues tagged with things like Help Wanted and Third Party, and maybe a good first issue, maybe not a good first issue. It's not listed here. Anyway, so that's what's going on in the core, and I'll just spoil it a little bit for you in the narrative. Dan hopes to release the next beta of 8.1, hopefully this week. So that's what's going on in the core. Thanks. Okay. Thank you, Jeff. And I'll just note, part of the reason, I closed a lot of open draft pull requests, mostly boards that had stalled for one reason or another, and so they could be reopened later in the future. And I also did some triage and issues, which is why there are so many that were closed. But there were also a lot of fixes, which is really nice also. All right. Next up is the libraries, and Katnie, are you able to read that? Yes, I am. So this section applies to all of the Circuit Python libraries, which includes the Adafruit Circuit Python libraries, which is everything that starts with Adafruit Underscore Circuit Python underscore and our community bundle. So all libraries submitted by community members to that bundle as well. So across all of those repositories, we had 12 pull requests merged by six authors and five reviewers. There were three that were 31 days or older, which was excellent to see that we're still keeping up with older PRs. And it leaves us with 39 open pull requests. There were nine issues closed by six people and five open by five people, leaving us with 600 open issues. 74 of those are labeled good first issue. If you're interested in contributing to Circuit Python on the Python side of things, you have a couple of options. If you're interested in reviewing, either way, visit circuitpython.org slash contributing. If you're interested in reviewing, check out the list of open pull requests. If you have the hardware for something, test it. If you don't, then take a look at the code, see if you see anything obvious. And you can leave us a comment and let us know. And if that works out for you, we can talk about leveling you up to the review team. If you're interested in contributing code or documentation, check out the list of open issues. They are listed out on the contributing page by repository name. And you can search that and see whether there's anything you're interested in working on. Leave a comment. Let us know that you're working on it. And we can help you out with any of that. If you're new to everything, which is to say Git and GitHub, there is a guide available on the Adafruit Learn system and contributing to Circuit Python using Git and GitHub. And you'd want to choose a good first issue. Those are issues identified as issues that will work out for folks who might be new to things. And we're always available on Discord to help. So don't let that intimidate you. Just find something that interests you. And we will help you contribute in a way that works for you. In terms of library, PyPI weekly download stats, we had 103,970 downloads over 309 libraries. And the list of the top 10 downloads for this week are in the notes. And library updates in the last seven days, we had a few updated libraries, but no new libraries. And so that's where we are at the libraries. Okay. Thank you, Katny. Okay. And next up is the Blinka section. Melissa, where are we at? Yeah. So Blinka is our Circuit Python capability layer for MicroPython, Raspberry Pi, and other single board computers. Looks like the stats were kind of pulled before today. So it doesn't look like much activity, but there were zero pull requests merged. Looks like there are seven open pull requests. And amongst other repositories, there was zero closed issues and three opened by three people. It leaves a net of 97 open issues. And there were 14,391 PyPI downloads in the last week, 12,308 PyWheels downloads in the last month, and we are at 100 in one port. And that's it. Okay. Thank you, Melissa. Okay. Next up is 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 will go down the list alphabetically to give everyone a chance to participate. If you are text only or missing the meeting, I'll read your notes when I get to them in the list. All right. So first step, I'll say what I, I'll give my Hug Report. Thanks to Fomigai and Narodak for noticing that the fetch sub modules change, which was a get sub modules thing in the Circuit Python repo, didn't really work very, didn't work for relatively current versions of Git that are in, say, the latest Ubuntu and things like that. Even though I had been using a more recent version of Git, and it worked for me, I should have checked it more carefully. So I have more about that in status updates. And next up is C Grover, who's now at the meeting. So I'll read theirs. Thanks to the team and community members who concentrated on improving Circuit Python support for ESP boards. Reliability and performance have improved dramatically. And the next step is D-Day Devon 3. I'll read theirs also. Thanks to Cat, E, Anecdata and Narodak for helping me figure out a simple read switch issue for my mailbox project. If you use both digital IO switch direction and switch pull in the wrong order of operation, the pin will remain floating, which causes random erratic behavior. There was a consensus that the Learn Guide should be rewritten. Okay, we'll take note of that. Thanks to Scur and Hem and C Grover for helping with the new custom board for my mailbox project. I was making it more complicated than it needed to be. Thank you for the great advice. And thanks to Cat and E for the excellent mailbox guide. Haven't even started on the low power portion of the project, but it's great knowing the next step is already documented. And next up is FumiGuy. All right. Thanks, Dan. Hug reports this week for me. Thank you to Narodak for helping identify the cause of the Fetch sub modules issue that I ran into, as well as unrelated to that, but also Narodak, I believe, added to the core and certainly pointed me towards some examples of devices with built-in I2C displays, which I was looking at over the weekend. So thank you to them for that. Thank you to you, Dan, for adding the fallback logic to Fetch sub modules, as well as pointing me towards the way to get that newer version of Git that you mentioned. Thank you to on GitHub, the user Bifobare, who's made over the last while several improvements to the Ethernet library, the Wisnet, I think it's 5k library, as well as working back and forth with me through feedback during the process on all those PRs. Hug report to Jose Davide for new functionality inside Bitmap tools in the core that's been PRed, and then a group hug for everybody. Thanks. Okay. Thank you. All right. Next up is Jeff. Hi. So I have a couple of hugs. One for you, Dan, for testing and finding two important bugs in the PWM audio out implementation on IMXRT, including the Metro M7. To Ketney for chatting and listening to me lecture about MOSFETs when it was totally irrelevant to the matter at hand, and a group hug. Okay. Thank you. All right. Next up are Jose Davides. Thanks to S-OL for submitting a PR for fixing the Talgrid flip function in good display IO. Yes. Thank you for that. Okay. Next up is Ketney. I'm busy telling other people to do things for the meeting and not doing my own thing. Okay. So first up, I have a hug for DJ Devon 3 and Paul Cutler for joining the brand new 3D printing helper's role on Discord. If you need assistance with 3D printing, they are around already helping a bunch. And so basically nothing will be changing there. They will just be more obviously, obvious when they're available. Thanks to Scare for suggesting the new role and those that would be a good fit. To Dan and Naradok for attempting to help me with an issue updating my local circuit Python repo. It turned out to, it turned into a fresh clone, but I left the other one in place in case we can figure out how to fix it. Thanks to Mr. Certainly for helping out with a talk proposal and talk content for an upcoming presentation for the PyCon Education Summit. Thanks to Todd Bot, Tammy Makes Things, Tectric, and John Park for contributing a personal moment each to my talk. Thank you to Maker Melissa for adding the Feather RP2040 DVI to circuitpython.org slash downloads and a group hug. Okay, thank you. And that reminds me, your first item about the 3D printing helper's role, also thank you and whoever else helped you getting the little icons in for the roles, which are very cute and useful. You are welcome. That was a group effort on the part of a bunch of the Discord helpers and myself and also Phil because I can't, only Phil can edit the admin role, so to get the admin icon put in, Phil had to join us as well. Okay, all right. Okay, next up is Maker Melissa. I wanted to give a hug to s-ol for fixing the title curve issue in Blinken Display IO and group hug criminals. All right, thank you. All right, next up are three people who are out so I'll read all of theirs. First, Mark Gambler. Thanks to Dan H for helping me get when I yet again broke APR by trying a rebase. Yes, rebases are easy to screw up. And it happens to happen to me too. All right, next is Tammy Makes Things, but who's text only, so I'll read theirs. Thanks to Cadney for wonderful conversations and support lately and a group hug to everyone for being awesome. This community is amazing and I'm glad to be a part of it. All right, and finally, from Scott, thanks to Dan H for swapping meetings with me due to Ari. That's his son being sick today. Okay, all right. All right, next up is Status Updates. Status Updates, let me put a timestamp here. Oops. Status Updates is our time to tell folks what work to individually. I will start and we'll go through the list alphabetically. 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 tips and tricks relevant to what people are working on. If a discussion becomes too long for Status Updates, we can move it to in the weeds. Okay, so I'll start with my Status Updates. I updated the tiny USB library in Circuit Python again and probably happened a few more times. There are a bunch of new additions and changes having to do with USB host and there'll be more. Also, there was tiny USB removed, the Git submodules in it and there's a different way to add submodules now that involves a Python script. So it makes it less likely that when you add the submodule and update the submodules in casual way, it will bring in all kinds of unnecessary stuff. As I mentioned, it's kind of alluded to in Status Updates. I changed the way Make Fetch submodules worked in the Circuit Python Make file, the top level Make file, to use partial clones, which is a really neat feature of Git that basically does a lazy fetch of things in a submodule so that you don't have to fetch everything but all the metadata is there so that if you need something and ask for it, it'll get put there automatically. This solves some problems that were present when we were using shallow clones as submodules. Something was a shallow clone, you couldn't find out its tags easily and you couldn't move back and forth in time but it turned out that not everybody had this so I changed this so that there's a fallback to the old way of doing it but I would encourage you to update your Git if you can and also I added Make Remove Submodules which cleans out everything so that if your fetch submodules get screwed up in some way or some aspect of submodules changes like we changed what submodule points to where, this will help you clean up that. I'm wrangling a bunch of changes to the main branch to get an 810 beta.1 out soon. I would hope that would be like within the next few days because there's only a couple more PRs that I need to approve before I feel like it's ready for the beta. I worked for some on the Animated GIF code, Gambler, Mark Gambler 21 had some fixes to Animated GIFs but it caused some builds that were on the edge of being too full to overflow so I figured out a way to save some more space there with some compiler options and it should be good for a while. I did some minor fixes including on the MetroM71011 board the airlift serial pins were flipped around due to a difference in the way the schematic was labeled and I've started to work on i.mx issues starting with a complaint from a while ago that BitBang.io was not working properly and then finally somebody over the weekend was trying to do raw HID and was having trouble and it turns out it doesn't really work right and I think I have a way to get around the problems that we have and I hope that person will test it and hopefully it'll work. All right next up I'll read C Grovers take a time stamp. C Grover to improve some recent Wi-Fi reliability issues refactored the foundational AIO modules for a new version of the workshop corrosion monitor. The latest version of Circuit Python greatly simplified Wi-Fi connectivity and fears to be efficient enough to incorporate open weather map conditions along with the local sensor data to improve corrosion prediction and response. The new core modules are running a week-long reliability test so now there's time to pick up the next thing which is a Precision VCO project and PCB assembly pulled out the stencils, solder paste and tweezers and next up is um DJ Devon 3 who's not. Nope I am here. You are here okay great go ahead. Thanks to thanks to Catney for the ping. Okay I've come to the conclusion there's a problem with my Feather M4 Express or there's a bug with how it handles pull up and pull down with a switch just a real basic switch. It works with the Feather RP2040 and the ESP32 S2 with no problem but I just cannot get it to work with the Feather M4 Express. So if someone can help test that that has one just run a latest stable release in a real basic switch demo and we can see if that's actually a bug or more than likely just user error. I started on a duplicate 100 watt mailbox for my family member. The amplifier has a built-in Bluetooth classic 240 watt forum speakers four inches. I've already tested the speakers and the amp together they're very very loud twice as loud as my mailbox. I scrapped the idea of using the distance sensor for the mailbox trigger and instead going them to read switches which Catney did on her mailbox which is it's that is just a much easier way to do it. The distance sensor values are I mean it's kind of slow to update as well as being very power hungry and if it's in a mailbox you're going to want something extremely low power and the read switches just make the most sense. So I just swapped everything out to try to do the read switches and I want to thank Catney for the excellent Wi-Fi mailbox guide it has been a source of reference material during this project so thank you very much for that. I am gathering components to attempt a small image transmission from a 320 x 240 TTL UR JPEG camera from inside the mailbox using Laura RFM. I've seen other projects that have done that in particular I think it was Husky lens on MicroPython but we don't have that same kind of library so I'm not exactly sure how I'm going to go about that. I do know that you can take a regular color image and downscale it and image process it in black and white so that you can reduce the the amount of packets but it's still going to have to transmit sequential packets of a lot of data and then combine that on the other side. So if anyone has ideas on how to achieve that I would be grateful and what I'm up to. Okay thank you okay next up is FOMI guy. All right thanks Dan. Both last weekend actually this week so far as well I've been doing lots of testing in the Ethernet library review some of the PRs over there in particular I've gotten wire shark setup so that I can capture some traffic back and forth between the the microcontroller with its Ethernet feathering and the router that it's fetching its IP address from to try to help figure out any remaining issues with one of the PRs there that changes the state machine logic inside that library. I have still been fighting a little bit with some random like segmentation faults and other similar issues during builds of circuit Python but luckily it hasn't actually frozen my computer in quite a while now so I'm feeling good about that and another thing that potentially hopefully will have fixed it is I took the case apart and gave it a nice clean out including some of the air intakes which had gotten a bit dusty so fingers crossed that we're going to be all good moving forward on that one. I have been learning how to make device definitions I've never tried to add a device to circuit Python before so I've been practicing on some existing ones just copying it and tweaking a few things in particular I have made a couple of definitions for devices with what are you know technically external displays but wiring them up as though it's an internal one so it shows up on board.display just to figure out what all the parts that are involved in that are and hopefully get to a point where I'd be able to do it on an actual device that doesn't have a real definition at some point and then for this week I haven't taken a look too far ahead but one thing I know for sure I want to get into is checking out the bitmap tools PR that's inside the core and that's what I got thanks. All right thank you all right next up is Jeff. Hi so last week it seemed like it took a long time to get there but I got i2s out to work on the Metro M7 and I quickly followed that up with support for PWM audio out because they both use the i2s functionality internally but there are two pins that you can route the audio signal to and it comes out as a PWM signal and another thing that's really cool is you can mix at least 12 voices simultaneously using audio mixer that's with 22 kilohertz and 16 bit mono samples so that's a really cool advance in kind of the level of audio that we can do in circuit python since it's a 500 megahertz chip with lots of processing time. I changed some error checking in struct.pack to better match the core of circuit python now incorrect use of struct.pack with too many or too few arguments is detected and you get an exception and before it would just either treat all the remaining arguments as though they weren't needed or just ignore any access ones which was incompatible with standard python so that will be an incompatible change but I think we put it in 8.1 anyway even though it's technically a little incompatible it's only for code that was wrong. I fixed a socket problem on pico that was affecting 8.1 betas but not 8.0 and I've been working on a second guide using open ai's chat gpt which I teased unmasked it on and I hope it will be ready sometime this week so either check out my social media posts or wait for the guide to come out it's a lot of fun. Okay thank you all right next up is jose de vides I'll read theirs made a pr to make a circle with bitmap tools in the core that pr is currently under view made some library documentation reviewed prs created new sensor library for the magnetometer qmc 5883 l sensor and took a look at something called sphinx autodoc type hints project this extension will take type hints and automatically include the information in rtd that'll be interesting okay next up is catney hello last week started the feather rp 2040 dvi guide brought in a new community helper on discord created the 3d printing helper's role on discord added two folks uh they were hugged earlier I tweaked the circuit python.org libraries page a bit um when it was when it was originally written the community bundle wasn't as significant as it is now um and there's there's a couple other things that the wording was a bit odd um it doesn't really fit our you know uh current situation so I tweaked that around uh so that the bundles get basically equal billing um and made sure that the rest of the wording made sense I still have to go through it a little bit I thought with updating my local copy of circuit python did not figure out a solution but left it in place in case one comes up and cloned circuit python fresh uh this week finished the feather rp 2040 dvi guide uh the pinouts page needs one item updated the circuit python essentials template pages need to go in and they need to be prepared in a way that they can be shared with um a whole series of upcoming feather rp 2040 boards uh the arduino blink and i squared c scan pages require the board and then I have the power management factory reset pages um once that is done I'll be starting on the feather rp 2040 rfm stuff uh that board is not available yet so we need a circuit python board definition for it and then I'll do the fritzing object and the pretty pins diagram um two sort of complicated things that are necessary for all microcontroller guides and then eventually the guide and also eventually the rfm uh version of the mailbox project which was my original build of it um but uh l'more wanted me to wait until this board was available to do the rfm version of it so here we are um and I'm going to finalize the updates for the circuit python dot org slash libraries and pr that and then as time permits I'll be documenting my growlite and timelapse projects and in other news I'm confirmed to do a talk at the python education summit so it's time to get writing okay thank you and catney congrats on these summit talk okay next up is maker melissa hello um last week I finished uh a check gpt powered baron up to show a demo on show and tell and I worked on testing various um text-to-speech software in order to find an improved voice and I fixed some issues with my code and circuitry which had resulted in some overheating and damage parts um I added and I also added the dbi feather to circuit python dot org this week I'm working on writing a guide for the chat gpt bear and I need to hack together another bear and update the photos as I write the guide and that's it all right thank you and now the last two are people aren't here so I'll read theirs first Tammy makes things um well Tammy makes things is here but not uh doing voice today last week started reworking my website to focus on project write-ups for projects I've done and doing and started writing up some of those things working through some chi-cat tutorials designing a small audio amplifier circuit for an un-coping project for my nephew which is making a map of sound with an oscilloscope since he's very into maps right now this week trying to get more stuff more of the stuff I'm working on documented on my website I'm hoping to jump off from the chi-cat tutorials of working on to create my own minimal rp 24 rp 24 rp 20 40 board as learning exercise and now building the audio amplifier I'm designing hopefully more but I'm not sure another news I want to give a hearty thanks to the community for your support and understanding as I've been awl recently I'm dealing with some pretty challenging medical stuff right now but we finally have a hopeful path forward I'm hoping that in the next couple weeks we'll pin down what the path back to health is and soon I'll be able to return to doing all the things that I love all right we'll uh get well soon say from all of us and finally um from Scott Tanute uh we take a time stamp here um working on supporting the rest of the imx arty evks the 1020 and 1050 work but the 1040 is weird I've made a script for generating pins and pinmuxing arrays for chips look briefly into speeding up flash reads and there is room for improvement there we'll need to add a way for reconfiguring flash after boot up because tiny u of 2 will use conservative settings all right so we're all done with status updates um and now we have the in the weeds section which is an opportunity for long-form discussions that either come out of status updates or that folks have identified ahead of time if you have any in the weeds the topics please make sure they get added while we're discussing other things so we're not waiting around to see if anyone has topics so I just have a side mention here um one of the things I didn't put that's in the python for microcontrollers newsletter but I didn't put up top is um arduino is um coming out with a new board that is kind of a I think meant to be the next generation regular arduino board it's the r4 board the current arduino board which uses an avr and that mega 328p is called the r4 and it would be releasing in may you can read about it on the arduino.cc website website it has a five volt renasus cortex m4 chip that chip has 256 kb of flash but it only has 32 kb of ram and it has no external flash um unlike most circuit python boards so um you may think that this board is kind of interesting but it's not probably going to be not really a great circuit python board it's sort of like in some ways similar to the sam d the arduino zero board which is an m0 processor um and was 3.3 volts and also had 256 kb of flash and 32 kb of ram so the m4 has hardware floating point but otherwise there is not a lot that we could take advantage of here like so the circuit python the circuit pie drive for instance would be need to be inside part of the 256 kb of internal flash so this is kind of like a kind of a souped up um uh trinket or something you know it has more pins than that but uh and it's five volt compatible which makes it kind of interesting maybe for some applications the other thing about this board is that interestingly there'll be a version with an optional esp32 s3 wi-fi um coprocessor and of course that means esp32 s3 is a far more capable processor than um the smaller renaissance chip i mean these in terms of memory and stuff so it's it's a little bit the uh the tail wagging the dog i'm not sure but it will be a coprocessor other than that we don't know too many details because i'm just because it will be talked about a lot i just kind of wanted to uh set some realistic expectations about it all right that's it anybody else have anything else they'd like to talk about all right we will wrap up so um next week um thank you this has been the circuit python weekly for uh march 23rd 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 from the adafruit shop at adafruit.com the video of this meeting will be released on youtube at youtube.com slash adafruit and the podcast will be available in major podcast services this meeting will also be featured in the python for microcontrollers newsletter you can visit adafruit dot adafruitdaily.com to subscribe the next meeting will be held next monday as usual at 2 p.m u.s eastern and 11 a.m u.s pacific time um and uh just remember that you can the meeting will be on discord just like it is now and if you want to be notified you can ask to be added to the circuit python is this role on discord so see you next week thank you everybody and i will stop recording