 All right. Hello, everyone. This is CircuitPython Weekly for Monday, April 10th, 2023. This is the time of the week where we get together to talk about all things CircuitPython. I'm Liz. I'm sponsored by Adafruit to work on CircuitPython and other things. CircuitPython is a version of Python designed to run on tiny computers called microcontrollers. CircuitPython development is primarily sponsored by Adafruit, so if you want to support Adafruit and CircuitPython, consider purchasing hardware from Adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join anytime by going to adafruit.it-slash-discord. We hold the meeting in the hashtag circuitpython-dev-text-channel and the circuitpython-voice-channel. This meeting typically happens on Mondays at 2 p.m. Eastern, 11 p.m., 11 a.m., rather, Pacific, except when it coincides with a 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. We also send notifications about upcoming meeting via Discord. If you would like to receive these notifications, ask us to add you to the CircuitPython-Nista's Discord role. There is a notes document to accompany the meeting and recording. The file 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 a link to the next meeting's notes document in the CircuitPython-dev-channel on the adafruit Discord. Check the pinned messages to find the latest notes doc so you can add your notes for the following meeting. If you wish to participate but cannot attend, you can leave hug reports and status updates in the document for us to read during the meeting. So, this meeting is held in five parts. First part is community news. Let's look at all things CircuitPython and Python on hardware in the community. It's a preview of our Python on microcontrollers newsletter. Second part is status CircuitPython, libraries, and Blinka. This is a quantitative overview of the entire project. It's a chance to look at the project by the numbers separate from our status updates. Third part is hug reports. Hug reports is an opportunity to highlight the good things folks are doing, taking the time to recognize the awesome folks in our community. Fourth part is status updates. Status updates is an opportunity report on what we've been up to. Take a couple of minutes, talk about what you've been doing last week, since last meeting, and what you'll be up to over the next week. And the fifth part is in the weeds. In the weeds is an opportunity for more long-form discussions. These discussions can come out of status updates or be something you've identified ahead of time as too long for status updates. And that covers how the meeting will go. With that, we'll get started with community news. And this week, there's a new Raspberry Pi Python code editor. Beta Software is now available that allows one to write and run Python code right in the browser. Another cool item in the newsletter I saw was a playable and edible Dungeons & Dragons cake. And I think most notably, Sturka Python show podcast has returned today with guest Danny Staples. I listened this morning. It was a wonderful episode. This and more is available in our weekly Python for Microcontrollers newsletter, which it goes out via email on Tuesday mornings. Visit AdaFruit.com to subscribe to the newsletter. And thanks to Ann for putting the newsletter together. If you have any Python on hardware projects to share or find content you'd like to see included, please consider contributing to the newsletter. You can open a PR on GitHub, mention and underscore engineer on Twitter with hashtag Sturka Python or email cpnews at AdaFruit.com with a link. And also if you have gotten off the Twitter, the hashtag Sturka Python on Macedon is also a viable option. But that is the community news. And next up is going to be a stay of Sturka Python libraries and Blinka. And we are going to go to Scott to read the core. Sorry, I will read the overall first. There are 27 pull requests merged by 18 authors, 11 reviewers, and there are 15 closed issues by nine people and 12 opened by 10 people. And now we will go to Scott to hear about the core. Thank you, Liz. Thank you. Okay, numbers for the core. 13 pull requests merged from 11 different authors. Waptang, Tess, Tess are new names to me there. We have five reviewers, which is more than normal, which is great too. Lady8m, Micro Dev, and Dave Pups are infrequent reviewers. So thank you to them. We have 23 open pull requests, which is not too bad. It's under that one page threshold, which is great. A number of them are drafts, and a number of them are brand new, which is great too. Issues-wise, we had eight closed issues by six people, five opened by four people. So a good number of people involved, and we're net down issues, which is great. We have a total of 631 open issues. We have eight active milestones. We have no issues open for 80X, which is great, and the highest priority for us funded by Adafruit to work on. We have 15 open issues for 8.1, which we plan on triaging this week to determine how to get 8.1 stable and out the door. We have 68 open issues in the bug category for 8X, which maybe we should triage as well. And then we have 20 open issues for 9.0, which will likely be our next kind of stable release after 8.1. And that's basically it for the core. Thank you so much, Scott. And now we're going to hear from Paul Cutler today for the libraries. Thanks, Liz. For the libraries, we had eight pull requests merged from seven authors with six reviewers. We had 48 total open pull requests. We had five closed issues by four people, and seven opened by six people. We have a total of 607 open issues with 73 being marked as a good first issue. For the libraries, the PyPI weekly stats, we had total libraries downloaded with 73,292 PyPI downloads over 310 libraries. And you can see the top 10 libraries in the notes. And for the week, we had three new libraries. That includes Adafruit Circuit Python We Classic, Circuit Python Async Buzzer, and Circuit Python BMI 160, which I believe is a sensor. And that's it for the libraries. Thank you, Paul. Next, we're going to hear about Blinka. I believe Melissa is out, so I can read. There were six pull requests merged by four authors and four reviewers. There are six open pull requests, two closed issues by one person and zero new issues. There are currently 93 open issues for PyPI downloads. And last week, it was 13,414 PyWheels downloads. And the last month, there are 16,432. And number of supported boards is 101. And that is the state of Circuit Python, libraries, and Blinka. And next up is going to be Huggerports. And Huggerports 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 alphabetically to give everyone a chance to participate. If you are text-only or are missing the meeting, I'll read your notes and then when I get to you in the list. So I will start. So this week, Huggerport Catney for a good chat last week. Huggerport to Carter for U2IF resources and assistance and a group hug. Next is Sea Grover, who is text-only. And he has Huggerport to FOMI guy for introducing Bitmap Tools in one of their streams. It made a huge difference in simplifying and improving performance for graphic object animations. Decaymatch and the 12 contributors to a surprisingly useful Bitmap Tools module, exceptional design and implementation. I'm still discovering all it has to offer. And Catney for a discussion about thermal camera features and operational characteristics and other interesting subjects has given me a new perspective about some useful improvements. And next is Charles B, who is also text-only and they have a group hug. And then next is Dan. Okay, thanks to Scott for fixing a pulse-in problem. There was some issue with background tasks happening. You can schedule background tasks or you can do them every tick. And there were just an incomplete fix to that. So thank you for fixing that, Scott. And thanks to Jeff, who's not here for a bunch of really wonderful additions to the SynthIO, a built-in library, which people who are interested in synthesizers are extremely interested in. And we'll see where that goes. That will be great. Awesome. Thanks, Dan. And I'm also excited about SynthIO. Next, I'll read for David Glau. Huggerport and NiraDoc for porting Lilygoe to watch 2020 v3 to Syrca Python and to FOMIGuy for his streaming on TR cowbell usage and coding. And then next is DJ Devin3, who is text-only. Huggerport to NiraDoc, Dan, Todd Bot, Betty2, Deshipoo and David G for helping to resolve the alphanumeric backpack I2C issue from last week's In the Weeds topic. Dan and Catney for helping me with Git. AnikData for helping me troubleshoot a new LED board issue. And Catney for the excellent RFM69 Learn Guide. One of the largest guys I've read yet, very well documented, can tell you put a lot of effort into that one. And next, we're going to hear from FOMIGuy. All right. Thanks, Liz. First up for me, Huggerport for Jose David, who has submitted a bunch of new libraries to the community bundle recently, as well as pops up in reviews across lots of other libraries as well. So thanks to Jose for that. Huggerport to Catney for a quest to add some interesting functionality to the conference badge and snake game from last year. That's a thing that I enjoy working on, so I'm happy to help add some new stuff to that. DJ Devin3, Huggerport, thanks for sharing a tip about known issue with certain models of NVME storage drives, the particular models that I happen to have. So that was good to know about some ongoing issues there. And Group hug for everybody. Thanks. Thank you. And next is from Jepler, who is away, but says hi from Boulder, Colorado. Take care all in Group hug. If you scroll up, you'll see some fun photos that he shared as well. Next is Jose David, who I think I am reading for. Catney for all the help and discord. T. Franks for documentation for the PN523 library and Fairbrain for adding the asynchronous buzzer library to the community library. And next we'll hear from Catney. I have a lot. So first up to how to Crayola for working on a 3D printed case for my in progress conference badge to FOMI guy for helping with me with badge code and the snake game that's going to be included. To see Grover for writing a slimmed down version of the improved thermal camera software to also be included on my badge. To Brent for looking into whether Adafruit IO works as I imagined it does and whether my plans for the badge mode of my badge are being dashed. It turns out that Adafruit IO does not work how I thought it should. So my plans are being dashed. So I have to come up with a new plan. To Tektrick for handling a thing over the weekend and seeing it through. To the Discord helpers. That's everybody in one of the helpers roles for a very thoughtful discussion over the weekend. To Phil and the more for helping put together two extra special items to donate to the Pi Ladies auction this year at Picon. To Mr. Certainly for help gathering content for my upcoming talk and a preemptive hug for the further help I expect to happen over the next eight days. To Todd Bot for some help with some audio cable questions. To ULiz for the same thing. To John Park for agreeing to help me with some Adobe Premiere questions this week so I can successfully edit a video of my talk quickly during Picon. And to Tammy Makes Things. Todd Bot, Tektrick and John Park for contributing an applicable personal moment to my upcoming talk and a group hug for everyone. Thank you so much. And next is Mark Gambler who's lurking. Hug report to Lady Aida and everyone else at Aida Fruit that puts board schematics in the Learn Guide. I was using them the last couple days to learn more to help me start my own project. And then we will hear from Scott. Hello. Okay. Hug report to Dave Fetz for debugging the pulse and breakage on ESP which figured this thing about the background tasks that Dan was talking about. Thanks to Dave for looking into that. Dave's awesome. Picking up bugs and running them down. I really appreciate it. And then Hug report to Apple Cuckoo for the code of conduct link fix that they did along with the documentation fix about uRandom on NRF. Thank you. Next I'll read for Tektrick. Katny for help over the weekend. All the Discord helpers for always helping out in a number of ways in the Discord server and a group hug. And then finally we'll hear from T. Franks. T. Franks, are you present? I'm not seeing them. Katny and Jay Pasada for helping me over the issues building RTD output in PyCharm for local reading and review. And that was Hug reports. Next up is status updates. And status updates is our time to tell folks what we're up to individually. I will start and we'll go through the list alphabetically. I'll call on you, take a couple of minutes, talk about what you've been doing since the last meeting and what you'll be doing until the next meeting. There's 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. And with that, I will get started. And this past week I've actually been doing more like circuit Python work than I normally do. I've been working with U2IF firmware and Blinka. U2IF lets you use RP2040 boards with Blinka and desktop Python. So Carter's done a lot of work with this previously and added a few Adafruit boards like the RP2040 QDPy and the just regular feather. So I just added the upcoming Thinkink feather which is going to have a port to plug in an e-paper display directly. And we'll be adding a couple of the other RP2040 bones feathers. So there's the radio feathers and the other one's going to be the CAN bus feather. So related, Lady Aida asked if I could try to add support for the seven color e-ink displays to the circuit Python EPD library. That's the library we're using with Blinka. And I have the display refreshing but only displaying in black and white which kind of goes against the purpose of having seven colors. So no colors yet and resolution might be a little off. So still work in progress but I think I'm close just because I am able to get to refresh and do all that kind of stuff as expected. So we'll see how that goes. And then next I will read for Cgrover. Continue to exercise bitmap tools for improving the precision VCOs graphical UI. Finally broke out of sandbox mode and will be wrapping up the prototype soon. Found two PCB changes that will be needed as a result and have an internal debate about choosing purple or after dark arch park boards. A happy dilemma. I've had that dilemma before as well. Spending some time today creating a small memory footprint version of the original Pi Gamer Pi Badge thermal camera should be fairly straightforward, famous last words. Also researching a recently discovered issue with 8.0.5 and display text not recognizing the width of a space character in a BDF font and throwing an error. We'll run some more tests and submit an issue if it turns out to be other than a cockpit error. Found a bunch of nails around the house and yard needing to pressure washer hammer yesterday. Trigger hand is a little sore today. And now we'll hear from Dan. Okay, Scott and I are going to do a have a meet and triage the existing bugs for 8.10 and 8.8x. So we can get an 8.10 out and figure out what we really need to fix for 8.xx. And the other thing is that the BNO-055 and there's some other sensors like the BNO-085 don't do ITC, ITUC that well. They do clock stretching and they have some other errors in their ITUC implementation. And so it causes the RT-1011 which is on the MetroM7 board not to work properly with the BNO-055 even though the peripheral on the board on the chip should do clock stretching. So after discussing this we're just going to try to put some fixes in the library to work around this problem. It is a known problem with these sensors that they make mistakes in their implementation of the ITUC protocol and some chips handle this and some chips don't. So hopefully we'll get it working on these chips on the RT-1011. That's what my thing next thing to do is to fix the library or make the library to work arounds. Okay, that's it. Thank you Dan. Next I'll be reading for DJ Devin. It was really neat to see a lot of people participating to help figure out the alphanumeric backpack I2C issue after last week's in the weeds topics. Dan did a fantastic job at troubleshooting the electronic circuit and helping to get I2C working. The culprit was initially hidden because I was using the ESP32-S2 which has an onboard pull-up just enough to pull up one backpack but not both. I switched to the RP-24E feather and the issue using I2C scan became more obvious the pull-ups on the backpacks simply weren't working. So from VDD to VIO is all that was required I would have never figured that out on my own. A small batch of new LED boards arrived I designed called Bleeding Rainbow. That's actually a band name and so very cool. It's a Neopixel stick made of 50 WS2812C RGB LEDs from World Semi. They're tiny 2mm LEDs and the smallest I could find with a built-in LED driver. Only red works at 3.3 volts Thanks to Anikdata for helping to figure it out. I'm happy to report they work great with circuit python and the board is cool to touch after hours of running. You can use one on USB power but not two. Windows threw an error about exceeding the USB power rating and shut off access to my feather completely. Power hungry little things. It removed the feather from Windows and no amount of power cycling helped. I had to use device clean up and reboot the PC to get the feather show up again. Power supply. They will be replacing the Neopixel strips inside my mail boom box. The house I moved into last year had an old goose neck faucet probably original to the house. It broke and sprayed water 5 feet in the air replaced it with a modern one that has a detachable head. No leak so far. That's good. And next we're going to hear from FOMI guy. Alright, thanks Liz. This week, or I should say over the past week I had a little bit less time to work on some circuit python stuff than typical. I have still been doing some swapping of hardware components inside of my main PC and I did end up opting to install a new OS because I could not get the previous one back to booting. But I'm pretty much up and running again on that. So I should have a path forward and I also have the backup computer as it is now dubbed set up that can do all the same stuff in case I still have any more issues. The work that I did do over the past week was looking into using two displays with display IO. There was some updates to display IO API a little while back, maybe a few months ago and I think that those updates actually were the root cause of some trouble on devices with two displays. Like the Monster Mask is the only one that's really built in like this. I did a couple of updates for one of the issues affecting that device and any others that used two displays but I think there's still some weirdness going on so I have been trying to trace through everything that happens especially when you control C reset and control D to run code pie again to figure out what remaining issues there are on that device. So getting closer but still have some looking into it to do. I have or I should say I will be working on some updates to the conference badge and snake game that I developed last year around PyCon adding capabilities to launch arbitrary external scripts as defined by the user so this way you can kind of show off whatever other circuit python project you want within the badge with just a couple of button clicks. And then this morning I also did do a round of looking up on community bundle PRs. There was a couple in there that needed to be merged from main so I got all of those updated and ready to go moved in. So that's what I have been up to. Thanks. Awesome. Thanks Tim. And next we'll hear from Katni. Hello. So this week I am wrapping up the RFM 69 guide. We published it without the circuit python essentials pages because obviously the rest of the guide was was in place and the essentials are a happy addition but not necessary to an original guide. So I've been working on those. I have four left. Two of those only require code so that is already written. And then I'm going to be adding one more page that has an RFM 69 basic demo of two boards talking to each other. One button does something to the LED on the other one etc. And then once that's wrapped up, I'll be starting the RFM 95 guide which is same as the RFM 69 but the physical radio module looks different so all the images will need to be replaced and the software is different so any RFM specific code will need to also be updated. So the RFM 95 guide should go faster because I can do a lot of copying pages from the RFM 69 guide and then just replacing images and code. But something always comes up so it should be faster but it might not. Then I will be this week wrapping up anything else that any other lease ends that need to be tied because I am preparing for Python this year. Some of the things I need to do in no particular order are finish up the PyBadge case and the software and thank you again to Tim and C Grover for your help with everything. I wouldn't have been able to do this on my own. I am still gathering hardware etc. for the open spaces and sprints filling in some gaps. I misplaced a bin from last year and there's a bunch of stuff in it that I need and it's gone. It's disappeared. I had it in January and it's just gone so I wrote it off and started working around it. I need to test my recording setup because I'm giving a talk at the Education Summit which happens before the conference and they don't record talks and a bunch of people expressed interest in seeing it so I need to record it myself and release it that way. I need to actually write the talk for the Education Summit and there's plenty more but those are the four things I could think of when I was writing this up. I'm going to talk more about PyCon in the weeds but that's what I've got for now. Awesome, thanks Catney. Next we'll hear from Scott. I was working on the IMX RT but I burned myself out with the 1015. There's these really weird errors where it just ends up in the ROM code or the debugger stops working and it's just really frustrating. I was talking about improving the flash stuff but I also realized that I probably can't do the XIP mode I was executing place mode I was excited about so I did it which we need to do in order to erase and program CircuitPy. I got my DVI feather I switched off the IMX RT stuff and I got my DVI feather on Friday and I was curious about getting that working in CircuitPy. I made pretty good progress I got it all set up and I got it compiling but it doesn't work. I had to break out the debugger or some pre-naps to figure out how to get the second core running. Speaking of not working last night I was going to run something on my desktop only to find that the root file system had gone into a read-only mode which is not great at all. It boots all the way to the desktop but nothing works because it's in read-only mode I've copied it to a spinning hard drive I tried to run the repair but it didn't actually fix any of the issues so I've got another drive coming today that I'm going to copy all the files off of that I can and then hopefully use that and hopefully be on my way so that's going to be my day-to-day probably once it gets here and I'm going to keep working on the feather DVI code because we're pretty excited about having display I.O. on a DVI display so that's it for me. Awesome, thanks Scott and I'm very excited about that DVI code and wish you luck with your computer issues Thank you. And finally I will read for Tectric Last week finished up some Arduino things and now resuming all my circuit Python work that was on temporary hold this week catching up on some PR reviews prototyping how the RP2040JSCI will work and looking at some Adabot upgrades patches that were identified a while ago and that concludes STAS updates so next is going to be in the weeds and in the weeds is an opportunity for long form discussions that either come out of the STAS updates or the folks have identified ahead of time if you have any in the weeds topics please make sure they get added while we're discussing other things so we're not waiting around to see if anyone has any topics but today we actually do have two topics so first we will go to Scott with their first topic Thanks Liz. I threw this in last week and I'm not sure it's super relevant but I wanted to bring it up anyway so somebody was using the Web Workflow and Deep Sleep Deep Sleeps traditionally worked with workflows is that because you're deep sleeping and you're optimizing for power you typically want to be really fast at waking up because of the shorter amount of time you're awake the less power you use and so typically with workflows including USB we won't start it up when you're waking from deep sleep however this person thought that was a bug but the goal request changed how it works so that the Web Workflow will start up after deep sleep I'm not sure whether that's the right thing or not but I wanted us to have a discussion about it their point I think was that like if I'm on Wi-Fi and I'm waking up one I want to access it and two I'm going to connect to Wi-Fi so I'm okay paying the penalty of starting it up anyway which is kind of I think the current state of 8.1 is that it will start the Wi-Fi workflow again what do people think of that? maybe we should make it configurable at least yeah I would definitely agree with configurable I think sounds nice if it could be a setting inside of the tunnel or however you would have to tell it to or false but somewhere where you could set it that way people who want to save power can do that and people who want to edit through the network can do it that way as well if right now you can just comment out the lines in the tunnel so is that do we need a separate Boolean or just right you're saying you can just turn off Web Workflow yeah like it's sort of like well right it's whether you can always turn it on or off by commenting it in or out you could also have a disable so that you only have to change one character or something like that yeah I'm not sure the tunnel is the right place because Mark is pointing out what I think is a pretty good use case which is like if you make it configurable you could do Wi-Fi every five minutes but take a reading every minute so make it supervisor at runtime or something so yeah but then you have to start it up late it started up late and you have to preserve memory I wonder if it's better as a boot.py thing is it started before boot.py or not it shouldn't be I don't think it is I think it started after boot.py that would be simple to add another Boolean right and maybe do you think we need a specific Wi-Fi Boolean or do we want to say like start workflows or remote workflow yeah I mean do we want do we want it to be a generic like yes I want us I'm I'm I could check I know I'm coming out of deep sleep I want to change the default from false to true that says start the workflows I think that I think I don't think we need both because I it's hard to imagine a case where you want to enable like if you're going to use the web workflow and the BLE workflow you would have entries for both and you would turn the both on or off and you would it just doesn't that doesn't seem like something you'd even wanted to control you can drill that through the Tommel file so it's less so just one one flag for all workflows yeah just one workflow for it was one flag for remote workflow I think would be I mean somebody might complain I want to turn them on and off right but your point is that for workflows in general you use the Tommel but pick the one that you want starting up and off you can pick that in the Tommel right so we only need a flag for you could also have web workflow and BLE workflow yeah but I'd rather just have like a generic workflow thing I would say remote workflow because you do have a workflow it's just through circuit pie or something like you know like there's always some kind of workflow so that's why I would distinguish but you don't have you like USB doesn't start up after a deep sleep and in fact you don't want to because it will prevent subsequent deep sleep oh I see what you're saying I see I see I see right like and this is this is why I made the the this is why I made web workflow not start up it's because that's exactly what right it's like I see it's like the K other case yes right like which is why I'm trying to make it like standardize it across workflows regardless is it possible to use the deep sleep memory to hold a flag so that you could say what to start up after wake up from deep sleep there is usually some I was assuming the user could use the deep sleep memory to do it yes so in boot in boots up high we just need to have a way of saying start up workflows or not right so you could just have a start workflow it's a few function rather than a I don't I don't want it to be a function because that because we're not going to start it while boot up what you're saying alright enable workflow I mean we have a bunch of functions right and it would default to false and you could also do that based on a button push or something like that deep sleep memory state yeah either case you might you might want to you could imagine a use case where you're not even worried about these it's just that you want to enable it or disable it based on whether a button is pushed right which is the advantage of boot up high yeah yeah okay so I'll file an issue about this and we should probably do it for a one yeah considering that the PR that I linked to changes the behavior for a one yeah so we should change it back but make it conditionalized right okay right I'll file an issue for that alright and next we are going to hear from catney hello again so Picon 2023 is coming up very soon I personally leave a week from this Wednesday the conference itself is the 21st of the 23rd that's Friday through Sunday and then there's development sprints afterwards for four days as for what Adafruit is up to we will be hosting open spaces during the conference we're looking at between one p.m. and three p.m. each day but I have to make sure that's even possible once we're there and the location is unknown until they put up a board as the conference begins and you know put up there when you want where you want to host so keep keep an eye on the Adafruit blog if you are going to be there and are interested in where and when those open spaces end up being following the conference we'll be hosting three days of development sprints which is an opportunity for folks to contribute to the circuit python project and or just have a simple introduction to circuit python everybody's welcome doesn't matter what level of expertise you have or don't have and so that'll be the 24th through the 26th I should mention that the open spaces are basically an introduction to circuit python via the circuit playground express I will be bringing a bunch of fun extras to attach to your express if you get beyond all of the features that are built into it and again everyone's welcome to attend and we will still have all that during the sprints so basically we can still accommodate folks who are new to everything and just want to dabble around I will be there from the 20th through the 27th on the 20th is the Education Summit which is a pre-conference event I will be giving a talk there I don't know whether registration is even still open for it so if you're attending and you're going to be there a day early you can check it out most of the time they can accommodate extra people it's never been an issue otherwise I am going to be trying to record that talk and then we'll post it and I can make a note in the circuit python dev text channel on the aid of fruit discord when that is posted so we will obviously Jeff Jeff and I are going to be there that's our very favorite Jeff Epler or Jepler and Jeff staying through the end of the Monday sprints I know Tartrick will also be there he will be helping us out with the open spaces first day of sprints as well and then remotely on the second to days of sprints so there's going to be a lot of things going on it's all python related obviously and I'm really looking forward to it I am in the middle of prep scramble which is pretty much how it always goes and if you are attending please reach out to me on the circuit python dev channel just let me know so we can make sure to meet up and if you otherwise if you're attending feel free to just find us around the conference you'll be able to find us for sure during the open spaces but we'll be around so you should be able to find us at some point we would really like to meet up with anybody who's going to be there and if anybody has any questions please let me know I can definitely help out at least with the stuff that we are hosting I don't know everything about the conference to answer general questions so that's it I just wanted to cover that because it's a week and a half away and I figure this is a good time to start discussing it and let everybody know what's going on I'm perfectly happy to accommodate remote folks during the development sprints if anybody wants to participate in the conference feel free and we will be able to chat on discord and contribute through github obviously or if you want to be available to help other folks that's also excellent and if you do please let me know that as well so I can be aware to look out for you during the sprints on discord that's what I've got we have a lot of work into python every year so looking forward to seeing how your top goes and everything this year I do put a lot of effort into it it's appreciated so thank you thank you alright so that ends in the weeds and we are going to go into the wrap up this has been Sergipython weekly for Monday April 10th 2023 if you would like to support Adafruit and Sergipython and those of us that work on Sergipython consider purchasing from the Adafruit shop at adafruit.com the video of this meeting will be released on youtube at youtube.com slash adafruit and the podcast will be available on major podcast services it will also be featured in the python for microcontrollers newsletter visit adafruitdaily.com to subscribe it comes out tomorrow morning the next meeting will be held next Monday as usual at 2pm eastern 11am pacific this meeting is held on the adafruit discord which you can join by going to adafruit.it slash discord to be notified about the meeting and any changes to the time or day you can ask to be added to the Sergipython NISO's role on discord we hope to see you all next week thanks everyone