 Hello everyone, this is the Circuit Python weekly meeting for April the 11th This is the time of the week where we get together to talk about all things circuit Python My name is Tim and I am working. I am sponsored by Adafruit to work on circuit Python Circuit Python is a version of Python that is designed to run on tiny computers called microcontrollers Circuit Python is an open-source project, but the development is primarily sponsored by Adafruit So if you want to support them 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 adafru.it We hold the meeting in the Circuit Python dev text channel and the Circuit Python voice channel This meeting typically occurs on Mondays at 2 p.m. Eastern 11 11 a.m. Pacific Except when that coincides with a US holiday in the note stock There is a link to a calendar that you can view online or add to your favorite calendar app that lists out all of the Meetings including the ones that do end up occurring on Tuesdays if that Monday is a US holiday We also send notifications about the upcoming upcoming meetings via Discord if you'd like to receive those notifications Just ask us to add you to the Circuit Pythonistas discord role There's a note stock to accompany the meeting and the recording the note stock contains time stamps to go along with the video So when you so you you can use the note stock to view only the parts of the video that interest you most and skip around as needed The meeting tends to run about 60 to 90 minutes So this gives you the option to skip around using the notes After each meeting we post a link for the next meeting's notes document in that Circuit Python dev channel on the Adafruit Discord checked the pin messages to find the latest note stock and you can add your notes throughout the entire week You don't have to add them on Mondays. We put that up In the about the hour or so following the meeting we put the the next meeting's notes up So you can fill those in at any point throughout the week if you'd like If you wish to participate, but you can't attend You can leave your hug reports and status updates in that document and then the host will read them during the meeting So this meeting is going to be held in five parts. The first part is community news This is a look at all things Circuit Python and Python on hardware in the community It's a preview of the Python on microcontrollers newsletter The second part is the state of Circuit Python the libraries in 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 are all working on The third part and the first of our round robin sections is called hug reports Hug reports is an opportunity to highlight the good things folks are doing take some time to recognize the awesome folks in our community The fourth part is status updates. This is our second round robin section Status updates is an opportunity to sync up on what you've been up to Take a couple of minutes and talk about what you've been doing in the last week since the last meeting And what you'll be up to over the next week until the next meeting and the fifth and final section is called in the weeds This is an opportunity for more long-form discussion. These discussions can come out of status updates If we you know start getting into a topic and it starts growing We may you know decide to bump that down to in the weeds We can discuss it further later on or they can be identified ahead of time and listed out down in that in the weeds Section if it is anticipated that they will be too long for status updates So that covers how the meeting will go First up is going to be community news. So let me take the time stamp for that Okay, a couple items from this week's python on hardware community newsletter We reached the milestone of 350 circuit python libraries this week Circuit python community reached a big milestone together on thursday. There are now 350 circuit python libraries The growth is steady and healthy for the project and there is a link listed here to the ate a fruit blog where there was a post Showing this occasion when it happened. There's some charts and other information in the post Second item today is a new version of circuit python Circuit python 7.3.0 beta.1 has been released. This is a new version of circuit python that came out last week Notable changes since the latest stable release 725 the notable changes are experimental mdns support usb to serial j tag support for repel on the appropriate boards Initial experimental usb host support Merging of micropython 1.18 changes Preliminary zlib module support and then gzip will be added later on to add more functionality to that Pio has new features wrap and wrap target have been added for support And then lastly keypad has had an enhancement to scan key states immediately upon creation You can see all of these items and more information listed on github under the releases page for the circuit python Repository which is linked here in the note stock as well Next up, we'll take a timestamp is a project from a member of the community this week. It's a I believe it's pronounced crooks radiometer. I am not a hundred percent certain, but this is An electronic crooks radiometer is an actual electrical instrument that basically measures light And this person has created a circuit python version of this using vector i o So they shared this in the show and tell channel. I believe on the discord and it'll be included in the newsletter There's links to github and youtube if you'd like to see the code or watch the video but it's a really neat implementation of a Circuit python visual widget. So if you're into that sort of thing, take a look at that next up Is remotely answering declining and hanging up calls on your iphone using circuit python and a and c s Todd bot has added functionality to the circuit python apple BLE notification service library to allow you to answer or decline and hang up the telephone calls Remotely using a circuit python BLE enabled device Connected to your iphone There are links here for twitter and github to learn more about that Next up is a usb midi controller. This is another usb midi controller This one is made with a raspberry pi pico and is coded with circuit python And there is a link to diy electro music website in order to learn more about this project All right, so those are A couple of the items from our weekly newsletter, however, there are many more So keep a look out for that coming to your inbox tomorrow To recap the newsletter. This is the circuit python weekly newsletter It's a circuit python community run newsletter. It gets emailed every tuesday The complete archives are available at eta fruit daily.com. There's a link again in the notes And it highlights the latest python on hardware related news from around the web Including circuit python python and micro python developments If you'd like to contribute your own news or projects, you can edit the next week's draft on github You can file a pr to do that Or if you don't if you're not set up on github or you'd rather not go through all of that You can also tag a tweet with hashtag circuit python on twitter or email to cpnews at eta fruit dot com So thank you to everyone who contributes project and news for the newsletter Next up is the state of circuit python the libraries in blinka So i'll read the overall section Overall this week we had 34 pull requests merged By 17 authors a couple of the names that i didn't recognize on the list this week So these may be newer folks to contributing Dom df coding Pontus oh Reese robinson and curt e those were the names that i hadn't Didn't recall seeing before so thank you to all of those folks and all the rest of our contributors across the circuit python ecosystem this week We also had eight reviewers And we had 24 closed issues by 11 people and 29 opened by 22 people So next up i will pass it over to i think jeff uh if you want to tell us about the core I would be happy to so the core is the c code that uh as a is at the basis of circuit python and um within the core we had 21 pull requests merged from 11 11 authors Including a couple of those uh that tim called out for being uh new or infrequent contributors. So thank You to dom df coding and curt e in particular um And race robinson is a name that is unfamiliar to me as well And thanks to our three reviewers. That was uh dan lemore and me In terms of pull requests, we've got 12 open pull requests Um that we need to take a look at some of those are held for version eight and most of the rest one Well about half of them are under a week old. So That's good. We just need to continue to keep on top of that Issues-wise we had 18 issues closed by eight people and 16 open by 12 people So it's nice to see the uh raw issues count go down a little bit and also uh participation from a bunch of folks Leaving us with 524 open issues When it comes to work that adafruit prioritizes We uh sort those according to milestones. So according to this list We have two open issues that we'd like to solve within the seven two stable release series And three open issues we'd like to solve before we release version seven three as the new stable release series And then we've got other lists for seven xx and version eight As well as libraries and long term issues And uh, it looks like we do need to catch up on assigning milestones to recently added issues And that is something that hopefully dan and i can get uh onto this week So as far as what is going on in the core, we've had a number of releases both a stable release seven two five And a beta of version seven three And it's really helpful if you uh check those out and let us know if they're working for you And especially let us know of any problems you encounter We can't test everything so we rely a great deal on our users helping us out by trying Alphas betas and release candidates. So, uh, thank you very much to everyone who does that and that's what I got for the core Alrighty, thanks jiff. Uh next up. I will pass it over to catney to tell us about the libraries Thanks tim So this applies to all of the adafruit circuit python libraries, which is everything that starts with under I'm sorry adafruit underscore circuit python underscore as well as a few extras such as our cookie cutter This week we had 12 pull requests merged from six different authors One name that wasn't mentioned earlier that is new to me is mkende Um, and we had six different reviewers One of the pull requests that was merged was 83 days old. So it's good to see we're still getting through older prs As well as caping up with all of our newer ones Uh, and that leaves us with 25 open pull requests across all the libraries We had five issues closed by four people and 13 open by 11 people leaving us with 630 open issues 198 of those are labeled good first issue If you're interested in contributing to circuit python on the python side of things check out circuit python.org slash contributing You'll find all of this information and more Um, including open pull requests and open issues If you are looking to get started reviewing take a look at the open pull requests Um, if you have the hardware test it if you don't check the code See if it looks all right to you leave a comment. All of that is super helpful And after you're comfortable with that we can talk about uh adding you to our review team Um, if you're interested in contributing code or documentation check out the open issues Um, if you're new to everything good first issue is a great place to start um And we have a guide on contributing to get and github I'm sorry contributing to circuit python using get and github and we're always available on discord to help out with that So don't let that side of it intimidate you. We want to help you contribute in a way that works for you In terms of library updates in the last seven days, there were no new libraries and the updated list was too much for this document Um, however, you can check out the library report if you're interested in seeing that massive list of updated libraries And that's what i've got All right. Thanks, kenny Next up I will send it over to maker melissa to tell us about blinka Yeah, blinka is our circuit python compatibility layer for Micro python raspberry pi and other single board computers And this week we had one pull request merged by one author and two reviewers There are currently four open pull requests And there was one close issue by one person and zero open by zero people leaving a net a 72 open issues And we had 12,923 pi wheels downloads in the last month and we are up to 88 boards And that's it. All right. Thanks melissa Steadily creeping our way up towards 100 there. That'll be a nice milestone Um, so the next section is going to be the hug reports section Hug reports is a chance for us to highlight folks in the circuit python community and beyond for doing awesome things As mentioned this section is held as a round robin where I will start and then we'll go down the list alphabetically Which is all of these are listed in that notes document Everyone will have a chance to participate If you're text only or missing the meeting But you have hug reports you can leave your notes in the document and I'll read off yours as we get to your name in the list Um, I will begin so my hug reports for this week are let's see here I had a hug for uh dan h and jeff for reviewing and offering some good suggestions on a core pr that I submitted Uh to dan h again for helping me get past an issue Uh where I had like an out of date version of something in my toolchain and it was preventing me from building successfully Um A user on github Uh for testing out my page layout and leaving a thorough review on the pr for it Um, hug report to catney for appearing on the upcoming deep dive stream to discuss circuit python library development and the work going into the picon festivities And my last hug report for this week is another github user named, uh bill van li woon van li woon 424 who um made their first contribution to circuit python. They Submitted a pr to add typing to one of the libraries this week. So congrats on the first contribution and thank you for helping us out Next up in the list is ask patrick w And I think it looks like ask patrick is not in the voice. So i'll read off, uh, ask patrick w's Um, and ask patrick has one hug report Which is to me a foamy guy for the great streams on friday. So that's good to hear that folks are Enjoying the uh the deep dives that i'm carrying on that's absence. So thank you to ask patrick Uh, and uh, next up is uh, lis blitz city diy So, uh, I've got a couple hug reports this week, uh, hug report to catney for proving my first solo new product guide She gave me excellent documentation. So I was able to follow along nicely Uh, hug report to eva for opening a pr get the tsc 2007 arduino library into arduino library manager. I didn't know that was a thing. Uh, so thank you Uh, hug report to dan h for pointing me to the tix library to use with the keypad library try and do um Long press and short press detection also wasn't aware of that. So it'll be good In handy, you know And then I wanted to do a hug report to ann for she proved three guides for me in one day last week That was a lot of work. So thank you very much All right. Thanks, lis. Uh, next up is dan Okay, thank you. Uh, thanks to jeff for fixing, uh, several outstanding bugs in 72x and for upcoming 730 They they've been languishing and jeff stepped in right in and did them Thanks to catney who uh, was frustrated about not be able to not having debouncing in the sort of playground library and Has figured out a way to use keypad in a very compact way um, thanks to naradok who, uh, has been experimenting with a bug With esp 32 s2 i2c and found a big clue that if you raise the frequency it works again Which really helps narrow it down and thanks to, um, lady aida for several, um fixes over the weekend for some, uh Customer customer issues about boards that aren't quite working right which we've gotten in already Okay, thanks All right. Thanks dan. Uh, next up is jeff All right, i have a group hug and then i have one for dan who had a much simpler solution to a problem that i was trying to solve about if type checking and Yeah, that's what i've got this week. Alrighty, thanks jeff Next up is catney Oof i was in the wrong window um So i have a hug report for jeff for helping me with what should have been a pretty simple concept in python But no one had explained it to me in a way that clicked until this weekend So thank you jeff for that. Um, thanks to dan for helping out with an idea. I had involving keypad and letting me talk through it Um, thanks to you tim for having me on your upcoming deep dive and a group hug Right, thanks catney. Uh, next up is k match Hey, thanks tim. Um, this may be a repeat hug, but uh, uh thought it's worthwhile to give jeff another big python A constrictor hug particularly for the frame buffer module Once i found a way of allocating some memory and pointing it to that it just kind of worked. It's amazing um, and a special thanks for Adding a few comments about which functions were necessary and which ones were optional so i could Focus on what needs to be done. Thanks jeff and thanks everybody Right, thanks k match. Uh, next up is maker melissa Uh this week i just have a group hug for everyone Perfect. Thank you maker melissa. Uh, and then the last for hug reports is tammy makes things Sorry, my phone decided not to unlock when i told it to unlock. Um, so i have a hug report for You foamy guy for the great, uh deep dives into display i o lately. I've been learning a lot that i know i'm going to use And then a group hug That awesome. Yeah, thank you tammy Uh, so that is the end of hug reports So next up we will do our second round robin section, which is status updates Uh, so a reminder status updates. This is our time to sync up on what we're doing The section is also held as a round robin where i will start and then we'll go through the list as they appear in the note stock Um Let's see everyone will have a chance to participate when i call on you You can take a couple of minutes talk about what you've been doing since the last meeting and what you will be doing Until the next meeting. This is also an opportunity to provide tips and tricks that are relevant to what people are working on If a discussion Starts to go a little long then we can move it down to the end the weed section to do at the end of our call So i will uh get started with this round robin Uh, so let me time stamp it here Yep, and then so, uh Last week for me, uh, I built the uh main sort of structural functionality for a tab layout widget. Um, right now it supports adding named tabs and switching between them from the code Um, I will be working on that this week as well Namely the things that need to be done are adding the visual tab icons so they can actually have Um little shapes that look like uh folder labels Um, and then implementing the touch input to be able to change between tabs right now The the code exists, but it's not actually hooked up to take input from the touch screen yet um sort of a Side project that I got started on while I was working on that tab layout is a uh a tile grid inflator utility This takes a small three by three tile sprite sheet and inflates it into a larger tile grid by repeating The center row and column tiles as needed to fill up to the desired size um, so my use case for this was the uh the visual uh little icon Images that are used in the tab layout, but I think this idea of being able to take a small sprite sheet and make a larger rectangle out of it Um, it will come in handy in a couple other places as well I have a few spots like buttons and other things that I think this will be helpful for um, I also started Uh from there peeking into the core a little bit inside of the tile grid object I was looking for a way to be able to update the bitmap Ordinarily when you create a tile grid, you give it a bitmap And there is not currently a way to change the bitmap So if you want a different one, you need to create a separate tile grid And there are ways you can create it and switch between multiple tile grids But it would be pretty handy if we could just switch An existing bitmap to a new tile grid So I dove a bit into the core to try to implement that functionality and I had a fair amount of success I submitted a PR with that and got some good feedback So I've got a couple of items to take care of this week in order to get that ready to go And that's a thing as well that I have in mind using it in this tab layout specifically making the difference between the active and the inactive tabs But I think similar to the inflator there's going to be lots of other display IO Use cases that pop up for this as well once we have this functionality This week, I also published a video on YouTube that shows the process of adding Type information to a circupython library So if anyone is interested in contributing in that way, there's now a kind of a video You can watch to get a peek at what that is like This week I am running the meeting today I intend to finish up the bitmap updating PR based on the feedback that I received Once that is good, then I will move back into the tab layout widget that I was working on And make use of that new functionality to set those active and inactive tabs And another thing I'd like to do this week is record another video that shows the process of making and submitting PRs I got some feedback on that typing video And somebody mentioned that it would be helpful to watch the creation and submitting of PRs So I figure we can make a video with that as well this week And possibly from there, I thought about as well It might be good to have one for the newsletter as well Like if folks want to see how to submit a PR to the newsletter Maybe we can make a video that shows that as well And that is it for my status updates So next up is AskPatrickW and I will read theirs AskPatrick has been working on a new board PR for the Wemos Lawlin C3 Mini It's building fine Now they just need to test all of the pin mappings And they're working out a process for doing that testing This is a when I have time type of project So the PR is in draft But if anyone has suggestions or feedback on the PR Feel free to ping AskPatrickW And the PR number is 6256 If you're interested in finding that in the core repository So next up I will send it over to Dan Okay Last week I debugged two unrelated UART problems on the RP2040 That was with board.ur and had to do with garbage collection And on the ESP32S2 that had to do with No, it's the other way around ESP32 was the other thing And RP2040 they started handling an additional interrupt In the SDK which we hadn't handled And it caused things to hang up So then I released CircuitPython725 to fix that To fix another bug that Jeff fixed And two other bugs that Jeff fixed Which were NRFPW and pinnail allocation and MP3 looping Then also released CircuitPython730beta1 Because it was about two weeks since the 730beta0 And we may as well catch up Because otherwise we can't point people to A named release to have them try the latest stuff It's much easier for them than to point them to Often to the S3 land stuff There's some problem with the release process The CircuitPython.org update job is not working properly So I have had to be running it by hand for the past several releases And I made a mistake when I did the 7251 And I did it in main So it thought that there were 725 releases for all the new boards that were in 730 So I redid that one and it seems to have fixed the problem Some people on Twitter found this So we had to respond to it to be able to To appear responsive on Twitter We were responsive We didn't have to appear responsive I reviewed a bunch of PRs from Jeff and from Lady Aida and other people I'm debugging a very weird I2C issue on ESP32S2 Somebody was trying to do motor controlling with a stepper motor And it ran really slow And it's because there was this 10ms gap between I2C transactions Which was ridiculously large And it seems to have to do with the frequency The I2C frequency The I2C code in the ESPIDF is really a mess And keeps changing There's a lot of churn in that code The workaround is to just choose a higher I2C frequency for right now And I'm also debugging some crashes of the ESP32SPI Code that is using the airlift It seems that what people see is that they Do a lot of requests And it might crash after a couple of minutes Or maybe 45 minutes or an hour, a couple of hours The problem seems to be present only when you use the portal libraries Like the PyPortal plus PortalBase But I tried a very similar example With the BearWare Wi-Fi and requests Stuff And I could not get it to crash several hours So there's something odd There's something about what the library is doing It's not necessarily anything wrong But it's different And it might be exercising a bug in the ESP32SPI code Okay, thanks All right, thanks, Dan Next up is Jeff Yeah, so last week I created a Python program For visualizing the content of a floppy disk Or more specifically a flex file Representing the content of that floppy disk And that is up on GitHub I finished up a pair of languishing PRs To add support for the .wrap feature Of the RP2040 PIO peripheral I fixed a problem with looping MP3s That affected at least SAMD51 I proposed some changes To allow type checking code to be optimized out of MPY files But Dan had a better alternative That didn't require any changes to the core So I ended up closing up that pull request And I spent some time this past week Reviewing pull requests as well So this week I have a fresh report Of MP3 playback problems to investigate From the forums, this time on RP2040 And I am trying again to get conversion Of disk images from the A2R format To the WAS format working And I had some success with that already This morning So I have a pull request out on that That I will be updating And I will make a one minute video About this flex visualizer program Just show a couple and explain what it's about So you can look for that on the Adafruit YouTube channel sometime this week Then we are really close to wrapping up the floppy So I have said that a lot But I think that the last thing Is to get the circuit python built in Floppy module And Adafruit Floppy library wrapped up So that means getting the core PR merged And then releasing the library And that is more or less it That does in fact reflect what we discussed In the internal meeting so that's good And then in soon news During May and June I'm traveling in Europe with my wife And if there are any circuit pythons Slash Adafruit slash cool people Along our travel routes I'd love to meet you for coffee or for a meal So there is a list of cities That we plan to be visiting in the notes document If that is where you are Or that's close enough to where you are That you might come in for the day Please DM me on Discord Or ping me out in a public channel If you are interested in working something out It would be cool I would love to meet anybody Because people are great And that's what I got All right, thanks Jeff That definitely sounds like a lot of fun Next up is Catney All right So this last week Merge the new dot get ignoring to cookie cutter The next step is to Adabot patch it across all the libraries Started testing PyLeap Immediately found issues One of which turned out to be a circuit python issue present Since after 7.1.1 Which is to say 7.1.1 works But 7.2x does not I provided feedback on some of the upcoming layout and text In the mockups And made a couple of feature request Feature suggestions as well And obviously filed issues on both PyLeap And circuit python for the Initial issue I found Which is that the code doesn't run until you hit reset 7.1.1 automatically reloads Wrote the async.io essentials template Deployed it to its first guide Had it reviewed by Dan for content accuracy Etc before sending it on to Ann and LeMore So that's finally ready to go Check it out in the ESP32S2 feather guide If you're interested It will eventually like all essentials templates Be in all the board guides that support async.io Verified that all references to the Adafruit Web Serial ESP tool were updated To the one that we're using That it was originally based on Found two that were missed And passed those onto Melissa to be updated I wrote the basic cutie pie charger BFF guide The Arduino demo wasn't working quite right So I did not include code in the guide The plan was to port the Arduino code To circuit python But until the math is corrected That's on hold And actually that's pretty much on hold until It comes up Like where the base guide has everything You need to know about what it does You don't really need to use code with it This week I already started fixing the Feather ESP32S2 pretty pins diagram To clarify the v-sensor Is being only a power pin And not having the other features of pin D7 Accessible from it And then I need to re-upload it to the guide And the PCB repo Update the front page images And the guide schematic and fab print and PCB files For the revisions on the Pi UART The BLE sniffer and PCF8523 I have a potential update to the circuit playground library I need to test whether it fits frozen into circuit python Before doing anything with it And then submit a PR if frozen fit is confirmed Added a property called buttons That provides a keypad setup for both of the buttons together So you can use the buttons with keypad Which includes debouncing and so on Required tweaking a few other things as well To make the library work with both the keypad button setup And the digital IO button setup It works great but again if it doesn't fit Then it won't be included Next step is the guide for the ESP32S3 Feather We'll be mostly mirroring from the S2 Feather guide Making sure the pages say S2 slash S3 Or simply ESP32 to make them agnostic to either version This next thing is not actually happening Like I said, the QDPI BFF guide is on hold And then continue testing PILEAP The plan is to go through all the available projects in PILEAP To ensure they work properly And then sort out a couple new ones To make sure that the adding a project process works as intended And then think about what further projects to add Which is either new or ported old projects And Jerry's not here But it turns out the ESPAT control library We're not going to archive it but we don't support it anymore So I need to add warnings to the repository To say that we no longer support it But you're free to continue using it And then this weekend I started PyCon Prep Went through what hardware I intended to have And sorted out what I still need Started organizing the hardware that I do have To prepare for travel And started writing the demo To include on the circuit playground Blue fruits that I'm bringing for the open spaces And that's what I've got All right, thanks, Katny Next up for status updates is Kmatch And thanks, Tim So I'm continuing on integrating large displays So-called dot clock displays That they can run with a new peripheral That's available in the ESP32S3 Called the LCD peripheral And along those lines I got to REPL So now the REPL shows up on this display Driven by the ESP32 and the frame buffer library So that was a big step for me Thanks to the frame buffer library But in the process I do observe some significant glitches At first I thought it was tearing Which I think is when you write to the frame buffer While it's actually drawing on the screen But in retrospect I don't think that's what's going on Since even a stationary image sort of glitches While circuit Python is doing calculations Even like multiplications and things like that And it seems to be affected with higher dot clock frequencies So I'm suspecting that the screen is going strange Whenever circuit Python may be accessing the RAM Or it's possible it causes some other delays That then the LCD peripheral gets slowed down And out of sync with where it thought it should be So along those lines I'm learning both on the ESP32S3 side What's possible and what the ESPIDF has to offer As well as what circuit Python can do And I think that driving this kind of display Is a little bit different than the other displays Like the SPI or I2C ones Since circuit Python may need to trigger this display To go refresh So I think there may need to be some coordination Between the display refreshing And when it's doing some calculation So just a few things here briefly I think right now the LCD peripheral Is just constantly refreshing the screen With its dot clock operation And that may get slowed down While circuit Python's doing something So I'm wondering if circuit Python can actually Communicate to this LCD peripheral Until it actually when it should go refresh So I can time it Also there's some callback functions Which I need to understand If maybe I could use that to coordinate between the two And then I assumed actually that the running at a high Dot clock may be the best So the amount of time to refresh the screen would be small So that then I could leave some other time For circuit Python to access RAM Or do some other processing But then I realized that's only the case If circuit Python is controlling When the refresh is actually performed So a lot of things in there to figure out And along those lines this week I need to make a list of all the glitches And things I see in different cases So there can be kind of a to-do list for that And probably put it on the issue that I've got But I'm thinking about taking a breather from that And actually working on a bowling training aid My daughter is in the high school bowling team And learning And I've been watching the coaches How they teach the kids And one aspect is getting feedback Of how you're doing is really hard It's hard to bowl and watch What the ball is doing at the same time So look at maybe having a position sensor To measure where you're throwing the ball Versus where you wanted to And maybe an LED strip Or something like that To show you where you hit it Versus where you meant to So anyway maybe take a breather And learn something about distance sensors And how to do that So that's my week Nice, thanks K-Match That definitely sounds like a fascinating project Next up is Maker Melissa Hello, last week I worked on updating The Whipper Snapper firmware uploader To use NPM packages Instead of pointing to other repos Which involved many changes And lots of bug fixes And I also finished updating guides That were pointing to the old ESP tool And I started looking at an alternative Mipi driver for the Raspberry Pi And this week I'll continue looking at that driver And I'll also check out a potential bug With Whipper Snapper that only occurred on Chromebook And that's where I'm at All right, thanks Maker Melissa And our final person for status updates Is going to be Tammy Makes Things Thanks, so last week I did more work on the Circuit Python card deck library that I'm building And I streamed twice working on that I'm trying to, on my stream, do a good job Of explaining the why behind the decisions I'm making and how I'm doing this So it's not going as quickly as it would If I was just coding it, which is fine And I had my last week in my old job So my schedule was ridiculous Including several multi-way code merges Of gigantic blobs of XML Which was a special treat This week I'm planning on streaming twice Wednesday evening Pacific time And Saturday around noon Pacific time And maybe a pop-up stream Friday afternoon Pacific time, we'll see how that goes Still working on my card deck library Hoping to get through all of the scaffolding This week so that we can start working On the fun display IO part I'm also doing a little bit of digging around In the Python standard library to see how hard It would be to bring in some more of the Funk tools stuff and also maybe data classes And I just started my new job Which is a Python data engineering job That I'm really excited about But my schedule is going to be a little bit unpredictable This week and probably next week too So that's what I got All right, thanks, Tammy And that gets us to the end of the status Updates section So the final section of the meeting Is going to be the in the weeds section As a reminder in the weeds This is an opportunity for more long form discussion Either things that come out of status updates Or things identified ahead of time If you have any topics for in the weeds Please make sure to add them at the bottom Of our note stock And right now we don't have any topics in the weeds So unless anybody adds something real quick Then I think we are good on that today If anybody is working on that I'll take this opportunity to mention For next week we actually have a slight change To the in the weeds section So basically next week we have a hard cut at an hour This meeting runs again anywhere from 60 to 90 minutes Typically it just depends how many people Are here for the round robins And you know how much stuff has happened during the week But next week we are on a schedule And we have a hard stop at an hour And due to that we are going to go without the In the weeds section next week So if you do have something to discuss You can add it to the document for the following week Or you can also always feel free to bring stuff up On discord anytime So with that I will also get into the wrap up here All right so this has been the circuit python weekly meeting For April the 11th 2022 Thank you to everyone who participated If you want to help support Adafruit and circuit python And those of us who are paid to work on circuit python Consider purchasing hardware 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 made available On all major podcast services It will also be featured in the python For microcontrollers newsletter You can visit adafruitdaily.com In order to subscribe to that The next meeting will be held as usual Monday the 18th of April And we'll begin at the standard time of 2pm eastern But we will have that hard cut at 3pm eastern To end for next weekend We went about 50 minutes today So if we do something similar next week Then we'll be in the perfect time for that So let's see this meeting is held on the Adafruit discord Which you can join at adafru.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 circuit python Easter's role on discord And that's going to do it for today Thank you to everyone who participated And we hope to see you all next week Thanks everyone