Hello, everyone. Welcome to the Circuit Python Weekly Meeting for October 17, 2022. This is the time of the week where we get together to talk about all things Circuit Python. I'm Paul Cutler, and I'm a volunteer contributor to the Circuit Python community. What is 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 them and Circuit Python, please consider purchasing hardware from Adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join anytime by going to adafruit.it-discord. We hold 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. Eastern, 11 a.m. Pacific, except when it coincides with a U.S. holiday. In the Notes Dock, there is a link to the calendar you can view online or add to your favorite calendar app. We also send notifications about upcoming meetings via Discord. If you'd like to receive these notifications, ask us to add you to the Circuit Python ESA's Discord role. There is a Notes Dock to accompany the meeting and this recording. The Notes document contains time stamps to go along with the video, so you can use the Dock to view only the parts of the video that interest you the most. The meeting tends to run 45 to 60 minutes, so this gives you the option to skip around. After each meeting, we post a link for the next week's meeting notes document to the Circuit Python Dev Channel on the Adafruit Discord. Check the PIN messages to find the latest Notes Dock 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. This meeting will be held in five parts. The first part is community news. We'll take a look at all things Circuit Python and Python on hardware in the community. It's a preview of our Python on microcontrollers newsletter. The second part is the state of Circuit Python, libraries and Blinka. This is a statistical overview of the entire project. It's a chance to look at the project by the numbers separate from what we're all up to. The third part 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. The fourth part is status updates. Status updates is an opportunity to sync up on what we've all been up to. Take a couple 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 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 identified ahead of time is too long for a status update. And that's how the meeting will go. All right, we'll start with community news. And the first one is the first ever Espresso developer conference is happening later this week and Lady Aida will be speaking. You can expect over 30 talks on topics including matter, the new smart home standard Rainmaker, the SB IDF privilege separation and more. The next piece of news is circuit Python 8.0 beta two was released. There's a link to the full release notes and be warned if you're using a raspberry pi Pico W. The circuit pie drive will be erased and reformatted. And you can click the full release notes to see everything that's changed since beta one. Next up is the Python developer survey 2022 share and learn about the community. The survey takes about 10 to 15 minutes and the PSF, the Python software foundation along with JetBrains is behind it. After the survey is over, the PSF will publish the aggregated results and randomly choose 20 winners who will each receive a $100 Amazon gift card. So let the Python software foundation know how you use Python, especially if it's circuit Python because we're part of the Python ecosystem and it's a chance to have your voice heard. Next up is the project of the week from the circuit Python weekly newsletter. It's very close to 10,000 subscribers so subscribe to the newsletter if you don't already get it and you'll see these kind of cool things. But the first one is a home rolled HP 16C calculator by Reddit user you slash some why OB it's a work in progress includes labels for missing keys. It uses a raspberry pi Pico a 16 by two LCD with level shifters and keypads with rows wired together to create a 40 key keypad learning Python along the way with Adafruit circuit Python. Next up, River Wang writes that the alpha version of the new circuit Python online IDE is out. If you want to help test it out, please visit the link that you'll see in the notes document. They apologize for the GitHub for it for being a little bit messy, but the IDE is going public soon. The circuit Python weekly newsletter is a circuit Python community run newsletter emailed every Tuesday. You can see the complete archives online at the link in the note stock. It highlights the latest Python on hardware related news from around the web, including circuit Python Python and micro Python development. To contribute your own news or project edit next week's draft or submit a full request with the changes. You may also take a tweet with the circuit Python on Twitter or email CP news at Adafruit.com. Next up, we'll go through the state of circuit Python, the libraries in Blinka. Dan, will you take us through? Oops, I'll read the overall first, I apologize. Overall, we had 49 pull request merge from 21 authors. Some of the new authors that look new to us are George bow, Zoni whoop, the D bar guy, I apologize if I'm mispronouncing any of these. Mopor, Calcutt, BMO, L118 and Boron Roni. There were seven reviewers. Thanks micro dev, Jephler, Gambler, Makar, Melissa, Tectric, FOMI guy and Dan. And 46 closed issues by 14 people and 29 new new issues opened by 22 people. And we are in the middle of a Hectoberfest and there were zero issues assigned the Hectoberfest label. And Dan, if you would do the core for me please. Okay, thanks. Okay, so in the past week, we had 30 pull request merge, which is ridiculous. 12 authors. As noted, there are some new ones. Thank you. We still have 14 open pull requests. We've gotten a lot of the hanging on ones out of the way and now mostly we're waiting for things that the really old ones are waiting for are not under our control anymore. So they're there, but we'll leave them open. There were 26 closed issues by seven people and 17 opened by 12 people. It says assigned Hectoberfest label to zero issues, but there are a bunch of issues that were assigned that label already. There are 574 open issues. There are zero issues for 73x. There were 26 open issues for 800. We got below 30 finally. There are 12 issues for 8xx.  So we're making progress on 801 and some of the issues like there were some issues that were fixed that were either just closed or fixed. I'll talk about that later in my status report. Alright, so it's looking. We are moving in a positive direction toward an 801 release eventually. Okay, I'm done. That's great to hear. Thanks, Dan. Ketney, will you do the libraries? Absolutely. So this applies to all of the Adafruit circuit Python libraries, which is everything that starts with Adafruit underscore circuit Python underscore. We had 17 pull requests merged across all of those repositories by nine different authors and reviewed by four different reviewers. In terms of those merged pull requests, one, two, three, four, five of them were 11 days or older, including one that was over a month. We can see that we're still bouncing around in those older PRs and obviously based on the rest of this list, still keeping up with the new ones. We have 27 open pull requests at this point across all of those. We had 17 closed issues by seven people and 11 opened by 10 people, leaving us with 567 open issues. 105 of those are labeled good first issue. If you're interested in contributing to circuit Python on the Python side of things, head over to circuitpython.org slash contributing. You'll find all of this information and more including open pull requests and open issues. If you are interested in reviewing, check out the open pull requests. These are places where if you have the hardware, please test it. If you don't take a look at the code, let us know if you see anything, sing tactic or misspelled or so on. And if everything was good, do you let us know that as well? It really helps. And the more you're comfortable with that, then we can start to talk about upgrading you to the review team. If you're interested in contributing code or documentation, check out the open issues. They're listed by repository alphabetically and listed out by title, so you can kind of get a feel for what one of them might be. If you're new to everything, check out good first issue as a label. We also have a guide to contributing to circuit Python using get and get hub, which will help you get started if you're new to those processes. And we're always available on Discord to help out. So we want to make sure that you can contribute in a way that works for you.  And preemptive hug report, thank you to everybody for keeping this going while I've been gone for two weeks. Unexpectedly. So that was really nice to be able to come back and see that things ran smoothly without me being able to prepare anyone to help with that. So thanks, and that's what I've got. Thanks, Catney. And now I'll turn it over to Melissa to talk about Blinka. Hello, Blinka is the circuit Python compatibility layer for micro Python and single board computers such as the Raspberry Pi. And this week we had two pull requests merged by two authors and one reviewer, leaving nine open pull requests there's actually three of these I know I've been merged in this morning but I think the statistics updated before that. And there were three closed issues by two people and one opened by one person that says there are zero. October, October festival labels on any issues but it's actually, we set it up as a topic so any of the Blinka related one should I make we get it. There are currently 84 open issues and it says we have 96 supported boards but I just added two more this morning. So that should go up next week. And that's it. Awesome. Thanks, Melissa. And that is the state of circuit Python, the libraries and Blinka. Next up is hug reports. I've got a couple hug reports the first one for Catney and maker Melissa get better soon. One for tech trick for keeping up on Hectoberfest and see I even while in the middle of moving and a group hug. Next up I'll read one for C Grover to tech trick and mark gambler for support of the recent communities bundle submissions. And next up is Dan H. Okay. Hold on. Okay, thanks to Jeff for fixing a wide variety of things both related to the Pico W Wi-Fi implementation and also many, many, many other malicious miscellaneous things which just seem to come to his head and then he has a fix immediately for them which is great. Thanks to micro dev or for some recent ESP 32 fixes of various kinds. Thanks to S curve for working on some Hectoberfest issues and finding a whole bunch that could be closed without any work because they were actually already fixed or or or moved in some way. And thanks to them. And thank you to all the people who noted an issue with the ESP 30 certain ESP 32 boards in beta.2, which we're fixing. Okay. Thanks Dan. Next up is DJ Devon three who I don't believe is here today so I'll read through those hug report for Catney forgetting COVID hope you feel better this week. Here's GCA 091 community library. The round displays are excellent for I projects approaching Halloween gambler reporting. Paint your dragons monster mass to the M for reporting. Paint your dragons monster mass code to the M for express, hopefully breaking out the U of two for all future I projects to run on any circuit Python board. And next is foamy guy. Hi report this week. Thank you to see Grover for some recent additions to the community bundle, which look cool and also more specifically for helping save me some troubleshooting time and frustration by pointing out a false assumption I was making about Redboard rails being connected. So thanks to see Grover. And then thank you as well to the ship who worked on PNG support for a to fruit image load library. And I got back into looking at that and that is now merged in so if anybody is interested in trying out PNG support that is in there. And I think that's a great addition to the display toolkit so thanks for that. And then a group hug to everybody. Thanks. Thanks foamy guy. And jeppeler you're up next. All right, I just heard about this PNG support so thank you to, to Disha poo for implementing it and foamy guy for merging it. That's really cool. Anyway, so I have a whole pile of thanks first I want to thank Liz for testing on the Pico w and a really great guide on the learn system. Let's get that out if you haven't already it shows a lot of ways that you can use the Pico w to do stuff online. Thank you Paul for hosting this meeting. I guess you posted once before but I was out or something so this is the first time around. You're doing great. And we hope to have you back many times. These are some GitHub user names. Hello on GitHub for fixing a Pico w bug that made MQ TT work that was reported by two users, including Liz to Dan age for another new release with so many good things in it, and a couple of troubles but you know, to bill 80 for picking up another Pico w bug and before bear for reporting and testing it this has to do with losing the USB connection while the board is connecting to Wi Fi. I'm excited to see the actions improvements itching towards completion and to DJ Devon three I love seeing your projects as they morph in the course of time. Remember to send them to send them to the newsletter when they get done. And that's what I've got. Thanks Jeff cat knee you're up next. I was about to go do something else in the note stock and realize no I need to scroll back up it's time. Okay, so I've been out for a couple weeks. If that wasn't obvious. I have a hug report to fill in the more for being so supportive. I had plenty to worry about but not being able to work was not one of them. To my partner rose for helping out so much while also being sick because she was doing better than I was and two friends and family for support over the last two weeks. To Tammy or chatting with me on the first day I was able to sit up for any period of time. Thank you for Melissa I hope you make it through having coded in the house completely uneventfully. In a more technical situation. Thanks to foamy guy for helping me with a Python script I had part of it figured out but I couldn't sort out parsing an RSS feed and generating a dynamic string based on three pieces of information from the feed. Tim had it sorted out in 20 minutes. Super helpful. Thanks to tech trick for always being up for library infrastructure tasks. We come up with a lot of arbitrary stuff and Alec is always excited to do it. Thanks to everyone here for keeping everything going while I was out I said that earlier during the library section but want to say it again. It's both nice and sometimes disconcerting how well things run without me around.  And this community is really amazing and obviously kept everything going very smoothly and a group hug. Thanks catney. Next up is Liz who's meeting them missing the meeting so I'll read them for her. Jeffers work on the Pico W and linking the issue that was causing problems with Azure. Dan for the U of two for testing the Pico W fixes and releasing the new beta in a group hug. And make your Melissa you're up next. I have a hug to Dan age for fixing the tests on the circuit Python PR I made to fix folders being able to move inside themselves and I had to get me for hopefully getting over covid soon in a group hug to everyone else. All right I'll read the next few the first one is from Mark aka gambler. He has a hug report for paint your dragon for such amazing code I keep finding myself modifying your projects and learning from them in a group hug. And next one is from micro dev who is text only. They have a group hug in a hug for Jepler for chained exception pull request. One for Dan H for testing and figuring out the bug and issue number 7070. Naradaq and M walla move for testing issue number 7060. Next up is Tammy makes things who is also text only. Hug for catney for a great conversation. Hug for me Paul tech trick and everyone else helping with the circuit Python community help desk in a group hug. Next up is tech trick who is text only. Hug for catney for all the good chats. Jepler for pinging me on a neat failure that happened in the CI always appreciate interesting problems. Another one for Jepler again because I haven't thanked them for all the awesome work on the pie cow. I'm very excited to get my hands on one and start tinkering. Hug report for Mark gambler for reviewing all my hacktoberfest PRs. And a hug for my girlfriend who while not a circuit Python user yet did move all of my electronics as well as everything else we own into our new home. And a group hug. All right next up is status updates. Status updates is our time to sync up on what we're doing. I will start and we'll go through the list alphabetically to give everyone a chance to participate. 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 up to 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 much for status updates we can move it to in the weeds. So last week I interviewed Joey Castillo for an upcoming podcast episode. Folks will know him from a lot of his products that use circuit Python like the LCD feather wing. This week this morning a new episode of the circuit Python show with Jim Muzerad of Micro Python came out today. It's great to talk with an upstream developer. And on a personal note I get my stitches out of my hand from my surgery a couple weeks ago tomorrow so I'm looking forward to that. Status update the next one is for C Grover who's text only. Last week submitted AD 5245 digital potentiometer driver and AD 9833 programmable waveform generator drivers as well as Shadow Watcher and punk console helper classes to the community bundle. This week we'll wrap up the current round of community bundle submissions with the PMSA 003I AQI calculator with a number of translations the SCD 30 CO2 indoor air quality calculator. Daylight savings time detector and adjuster, timing is everything. An ohms law calculator, a music helper library, MIDI note number to note name and note to frequency and descriptive MIDI CC decoder. A dew point calculator and a heat index calculator. Future planning to revamp the Cedar Grove widgets collection to take full advantage of vector display graphics and drop the support for display size independence. The widgets include an animated kitchen scale, LED multi digit bubble displays think HP 35 and emulations of a 65 magic eye, Neopixel strip and LED bar graph integrated circuit. Wrapped up this year's landscaping with a three and a half bag concrete project was nice to play in the mud again. Recently learned and was amused to hear that over 30 years ago, my son used to sneak handfuls of wet concrete from my patio and mowing strip projects to sculpt a secret rock collection. That's pretty cute. Dan, you're next up. Okay, so as mentioned, I released 808 to last Friday. Mostly this was a whole bunch of important changes, including Pico W, but it turns out it was so that was mostly really good. There were it turns out a couple of board families basically stopped working altogether, or at least partly ESP 32 C3 boards just boot loop and some ESP 32 boards, mostly older ones also don't work. And we thought that the cause was the same, but it's actually different. So we have a fix for the ladder. Thanks for working micro dev for working would be on that. And the C3 issue is caused by ESP IDF updating the version of the compiler that they're using. And there are no code changes that are causing this issue. So that's going to be difficult to figure out. It could be like the compiler is compiling code in a different way. And so some uninitialized variable has a different uninitialized value, or it could just be that there's a bug in the compiler. So we'll need to check on that. There was this issue of junk from stuff that was being printed out by circuit Python getting back into the REPL, which was really confusing. How could that happen? Because it's output going back into the input and Jeff figured out that on Linux, there's something called echo mode. When you open a serial port, it will echo stuff that comes in back to the output. It's output until you turn that off. All terminal programs basically turn that off up front. But there's a window of time where that doesn't happen. There's a race condition. So I put in a delay at a certain point and the issue seems to be mostly fixed now. It just makes the pieces of the status bar not appear as often. And also it's fixed on the NRF, which also had sort of an even worse manifestation of that. I did a whole bunch of reviews. So for the coming week, I will work on the ESP32C3 compiler issue to try to figure out what's really going on. I still have a bunch of outstanding PRs to review, and I will continue working on A to O issues as usual. And I will do a beta 3 really soon to get the broken ESP32 boards running again and to get in some new PicoW fixes. So expect that within the next day or two. If I can't figure out the ESP32C3 issue, I won't bother to include a fix for that in there. Okay. Thanks, Dan. Next up is DJ Devon 3, who's missing the meeting, so I'll read through some of his cool projects. Purchase some arcade buttons from the Adafruit store to use as reset buttons on all my S2 and S3 boards dealing with the hard reset bug. Hours later, the core devs fixed the hard reset bug. Still added a reset button to my social media counter out of principle, even though it's really no longer needed. Still working on adding the Twitter API for the social media tracker? Dealing with Twitter's OAuth has been a major headache compared to YouTube. I'm trying to add all the APIs using only the request library and avoiding using portal-based to maximize board compatibility. I created a YouTube video on my new channel called Devon's Workshop featuring a complete build of Adafruit's Trinket M0 Neopixel goggle kit for CircuitPython. Video includes a lot of soldering, updating the Trinket M0 bootloader, and installing CircuitPython 8.0 Beta2. Added a bug report for the ProtoMatter library as it's not playing nice with the UM Feather S3 and RGB Matrix Feather Wing. I tried everything I had to get it to work. It's just over my head. Got two GCA091 round displays running some ICE code from ToddBot. That cut my development time by a huge margin and was easily able to get a working demo within minutes. I plan on adding it to a new DragonSkull mask purchased for Halloween. This week I'll be working on turning the human eyes into lizard eyes. Will the displays fit in the goggles? Yes, but I actually want to wear the mask for Halloween so the projects are separate. It's a neat idea for lars or other stuffed animals to combine those two projects. If I finish with the eyes project in Twitter API early this week, I'd love to get back to the Laura Messenger project. I'm really excited to work with long-range communication boards. And next up is FoamyGuy. Right. Last week I worked on testing out the new Wi-Fi functionality in the PicoW. Belated additional HUD report to Jeff for the work on that. It's going really nice so far. One of the things that I worked on, so I did some stuff in requests. I also did some HTTP server examples and I found all the basic stuff working. I started building out a trivia game because there's a free trivia API that returns JSON to you. So it's a nice thing to test with. I started building out a trivia game for that. And on the PicoW I found an upper limit of the size that it seems like it will return successfully. I tested the same thing on ESP32S2 and it does seem to be able to return larger files in that environment on that port, I guess. And I have the example script and I have the sizes and everything documented. So I'll make a PR with everything I found on that hopefully later on today. Kind of evolving from there. I started working on display IO with the PicoW for the first time. Basically trying to build out a different way to make the trivia program. So the previous one was using HTTP server. So a person would play it either on a PC or on their phone from the browser. The new one though is only on a single device. It's all self-contained. It has a NeoKey one by four where you can press the buttons because lots of the trivia are multiple choice with four answers. So I've got the screen set up and I've got the NeoKey set up and the drivers and everything are working for all of those. I still intend to go back and kind of build out the rest of the trivia game to have it ask the questions and let you answer it with the buttons. This week so far today I should say I was working for a little while trying to get my core repo fixed up. It seemed at some point along the way I lost the ability to make the docs with make HTML. I think it's something to do with having an older version of Python. I have 3.8 and I'm thinking maybe that one's not supported anymore. Started updating some stuff and I think I did actually get a successful build just a few minutes ago. So fingers crossed I need to look into it a bit more but I think we might be in the clear now. I also tested out the that PNG support PR for image load. I had tested out that out in the past but it was on the hack tablet which is a bit of a more non standard device so I went back and did it on a feather TFT just basic device. Paired everything down to the absolute most basics and just got a nice simple test for it. And then submitted follow up PR for that with typing and with that simple test example included in it. And then on a sort of more personal note this week in particular tomorrow night is my last class at least for a little while so hopefully I'll have some more time in the evenings that I can start getting back into circuit Python stuff coming up soon. So I got thank you. Thank you. Jepler you're up next. All right. So a belated hug report to the more for teasing the first cowbell in her live show on Sunday night it's a great name if I do say so myself. Anyway what I've been up to last week was Pico W bug squashing some flash size savings PRs that let Dan put in a nice functional edition so I was excited about that. I reviewed some PRs. I prototyped chained exceptions for circuit Python, which makes raise X from why work more like standard Python and give you more information about the problems that occurred. I chased down several async IO problems and PR fixes. And I based on a report from Liz there was what looked like a Pico W bug but it was a bug in the Dottie and V module. And I chased that down and fixed it. I fixed some warnings within the circuit Python build due to the use of deprecated GitHub actions features. There may be more to do though. There's a certain construct they decided it's not a good construct and so you have to change your actions or update to newer versions of actions to resolve it. And last thing is IPR to change so that we run the async IO tests against a fruit circuit Python async IO during the CI process and find problems earlier. And as I mentioned earlier this is subsequent to actually fixing those problems enough that this would work and not just fail. Anyway, so this week, another classic keyboard was added to my list of keyboard projects. This is an Atari 8 bit era keyboard. I've been reading about them and they are weird. They have a freaky way that seems to connect up to 72 keys using just eight IO pins, but in a way that won't work with key matrix and this is all based on online reading. So we'll find out how this project goes. And another project that is not for circuit Python is I'm going to try building doom for the feather ESP 32 s3 based on some code that is on GitHub that works on another ESP 32 s3 device, which is that it would be fun to show that off running. Not a circuit Python thing but fun retro gaming thing. And that's what I've got and I'll probably do something else it's not on this list and not do have these things you know how I am. I agree, seeing doom run on that would be fun. All right, cat, you're up next. I am up next. All right, so last week in the week before I was out, I caught COVID. I'm working on sharing that situation on my blog if you're interested, which is at catty.com. This week, I have a ton of catch up. If you're on that list and you know it, please reach out to me to make sure I get to it. I am working still on the LTR 303 slash 329 guide. The plan is to basically just focus on that. And then I have a huge list of further new learn pages and guides. The plan is to finish the LTR guide and then revisit that list and make a decision on what's next at that point. That way I'm not trying to do a bunch of things at once. And if I talk to you about doing a thing, please don't hesitate to reach out and ping me. I am absolutely certain that I have forgotten things I talked to folks about. I, you know, forget what I say like 10 minutes later at the moment. So if you're blocked on me or if we talked about a thing or whatever, for whatever reason, please feel free to reach out to me. It's much better if you let me know that I've missed something than to let it go undone. So for any of these contacts, if there's anything in the last couple of weeks, or obviously in the weeks before that that we talked about, please let me know so I can make sure it's on my list. That would be greatly appreciated. And that is, that is all I have for this week. Thanks, Katny. Now I'll turn it over to maker Melissa. Oh, let's see where I'm at the time. Oh, yes. Last week I finished updating the tensor flow on Raspberry Pi for a guide to work with bull's eye and the latest PI camera to I updated the associated archive vision library which currently has a PR waiting so it's kind of broken at the moment. I mixed up a few miscellaneous GitHub issues. I added some missing boards to circuit python.org, and I tested out a text to speech library to see a text to speech library to see if it would work for future projects. This week I am going to I'm finishing updating screenshots on the code editor learn guide, and finally working on the guide for the clue robot I made for circuit Python day. And with COVID now in the household, it's uncertain how it feels week goes on, but I'm trying to get as much done as I'm feeling okay so far. That's it. Thanks, I hope you continue to feel okay. Next up is Tammy makes things who's text only so I'll read those. Last week rebuilt my Linux VM which had mysteriously stopped working so I can once again build circuit Python. Install the new beta version of loop back a Mac OS utility which I think hope will fix the OBS audio issues I was having with the Mac OS Ventura beta. This week getting ready to go out of town for birthday festivities. My birthday is Friday. So probably not a lot of circuit Python stuff happening this week or next week. Non circuit Python fun. I scored an HP 200 LX and the link is in the dock in old DOS based palm top computer from the early 90s on eBay and got turbo see turbo Pascal and turbo assembler installed on it. So I can hack stuff on the go. I wanted one of these so badly when they were new, but they were just too expensive and I'm excited to get one in my collection now. It's astounding to compare this hardware which had 80 C 186 running at 7.9 megahertz with one meg of RAM to a Raspberry Pi Pico that's one 100th of the cost. Happy birthday to you. And next up is texture who has tech text only. Moving moving and more moving finished all my October fest PRs reviewing incoming PRs as I found the time finalize the unified composite actions for the circuit Python libraries working on the build them. PY action was a huge help in personal projects my circuit Python. I can't say Hanukkah for some reason with circuit Python circuit Python Hanukkah project is now OSHA certified. Thanks to CERN for fantastic license options for hardware. Also in personal projects my circ link CL CLI tool for running code locally and having it auto push to circuit Python boards as it's modified is pretty flushed out and ready for use, hoping to use it for testing some PRs next week. This week in upcoming probably the last light week as I unpack everything and get the last few things out of the old place hoping to ramp back up possibly as early as the end of the week. Planning an end of October fest review on October 31. And after checking with the October discord I'll add the October fest accepted label to any PR submitted at or before that time so they count, even if changes need to be made. The PR will still count so please don't let that prevent a submission. Following through with the unified late library CI workflows and lastly odds and ends while planning where to start next week. Thank you everyone for your status updates. Next up is in the weeds, and I will turn it over to cat knee. Thanks Paul. So I just wanted to put this out there I will be working on the graphic for the circuit Python community help desk over the next couple weeks. I have ideas but I wanted to put it out here so anyone else with ideas or suggestions can collaborate please send me ideas via email at cat knee at a to fruit dot com as messages can get lost on discord. If you're up for it sketches are welcome. I'm hoping to work with our graphics person to get a few ideas sketched out before we finalize anything and if that happens that way, I will be sure to share all the progress with everybody as we go. If it's in the hands of our amazing graphics person it's going to come out great it always does.  But I would say 99% of the time even when I think I haven't explained something well. Brace produces something perfectly wonderful so I'm not all that concerned about it but I just wanted to let everybody know that that's in the works it's been in the works but I just haven't obviously had time. But since it seems to seems to be continuing. I want to make sure that we've got something that we can use as a as a YouTube thumbnail and also as a you know for for blog posts and in the newsletter and all that stuff. So that will be a thing very soon I hope. And that's my topic. Awesome. Thank you. So if you have any ideas make sure you email cat me. And the last up for in the weeds is mark gambler whose text only asks. Has anyone done any performance on display IO speeds, really more interested in whether it's worth me poking at. I think that there are probably some speed ups to be had a long time ago I had a conversation with Scott about that and he said well, you know his goal was really getting it functional and it didn't have that performance optimization. Steps so kind of. I haven't really started on any of it so if you have ideas or want to dive in and figure out how to profile. Oh and the ship who did look at some things. Briefly so I will step aside and let the ship who say if they have some particular ideas but yeah I also wish that it would be speedier and I don't think it's really had a look at the performance. Super close. Anyone else have any comments on that. Well then we'll wrap it up. This has been the circuit python weekly meeting for October 17 2022. Thank you to everyone who participated. If you want to support Adafruit and circuit python and those 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 on major podcast services. It will also be featured in the Python for microcontrollers newsletter. Visit AdafruitDaily.com to subscribe. The next meeting will be held next Monday as usual at 2pm Eastern 11am Pacific. The 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 date time or day you can ask to be added to the circuit pythonistas roll on discord. We hope to see you all next week. Thanks everyone.


It's time for the Lawn Jean Chronoscope, a television journal of the important issues of the hour. A presentation of the Lawn Jean Wittner Watch Company, maker of Lawn Jean, the world's most honored watch, and Wittner, distinguished companion to the world honored Lawn Jean. Good evening, this is Frank Knight. May I introduce our co-editors for this edition of the Lawn Jean Chronoscope? Mr. William Bradford Huey, author and analyst, and Mr. Eliot Haynes of United Nations World. Our distinguished guest for this evening is the Honorable Chester Bowles, former United States ambassador to India. Mr. Bowles, our viewers, of course, remember that you've been a distinguished former governor of the state of Connecticut, and more recently that you've had a most interesting tour of duty as our ambassador to India, where you attempted perhaps a new approach, and you've come back with a positive program for action in Asia. Now, first of all, sir, what would you recommend to us here in America? What would you recommend that we do about Asia? Well, I think one of the first things we have to do is realize some of the things we can't do about Asia. It's rather hard for us Americans to accept this, but we do have definite limitations, and I think a wise man or a wise nation accepts and understands its limitations. Well, do we have military limitations? Well, I would say that was our first one. I think every American general or military authority realizes and agrees that an all-out war on the Chinese mainland would be a disastrous mistake for America that the only country that would gain by it would be the Soviet Union. We'd be weakened in Europe. We'd be weakened all over the world. And I think the second thing we've got to understand is we cannot buy the friendship of Asian countries or any other people. We can't buy their friendship with money. Those two factors I think we should recognize. Now, you mean say that we can't rely on army or air force or navy to stop the communist threat in Asia and we can't stop it by giving dollars and economic grants. Well, I wouldn't say we can't stop it. For instance, in Korea, we moved in to face up to a clear-cut aggression on that Korean front. I think it was an historic decision. I think it was a good decision. It's been a long and frustrating struggle for all of us, but I think it was wise. I think we're also holy wise to move in to help the French stop communism moving into Southeast Asia and into China. If we hadn't done that, Chinese communism might have overrun all of South Korea. In the long run, these two things, military and economic aid, are not the answer to the communist threat in Asia. Because you cannot find an all-out decisive war on the mainland. Well, now, Mr. Ball, you've spent a long time in India and have gained quite a reputation for figuring out the answers in that area of the world. What do you think we can do to stop communism in Asia? Well, I think the first thing we've got to do is to understand that Asia, all the way from the Mediterranean Sea to Japan, is in a state of revolution. There's a revolutionary surge that's going right through that part of the world that affects almost all Asians. What's the nature of that revolution, sir? Well, it really has three sides to it. It's, first of all, a revolution against colonialism, a revolution for freedom. Second, it's a revolution against feudalism, a revolution for a better life, for a better economic opportunity. That's a revolution against, that's a class revolution, a revolution against landlord. That's right, to a degree. And third, it's a revolution for human dignity. The colored peoples of Asia have felt for a long time that they've been made inferior by the white West. They resent that very deeply, and this resentment runs deep into their souls. Mr. Bowles, you think that if the United States backed up the three parts of this revolution in Asia and supported those three parts and encouraged this revolution, that we would be able to stop the communist threat and safeguard Asia for democracy? Well, I certainly feel that you could build a free and dynamic Asia, or help build it, if we'll take that kind of positive position. You were saying, sir, that first of all, that since we have military and economic limitations, that if we are going to help the cause of freedom in Asia that we have to have men who understand the revolt in Asia. That's correct. And then we have to proceed and hope to win by a superior brand of diplomatic maneuver. Of diplomacy, that's correct. Well then, what program, what positive program for diplomatic maneuver? Well, let's start with Indochina. Now, in Indochina, of course, there are three separate little nations there, Vietnam, Cambodia and Laos. There's an all-out communist civil war there, supported by the Chinese. We're supporting the French in their efforts to hold that particular part of the world against communism. But the people are not particularly interested in the war. They're sitting the war out. They're sitting it out because they don't know what the purpose of the war is. We know it's to stop communism. They think in their minds it's really simply to allow the French to go on exploiting that country as a colonial power from Europe. The first thing we could do, for instance, is to make it very clear the people of Vietnam and Cambodia and Laos and the people of the world, that we would favor a free country, a free Vietnam, a free Cambodia, a free Laos as soon as this war against communism is won. You're aware. You think you could rally the people. You've got to rally the people and give them something to fight for. You think it's so important to let the people of Indochina know that we are against colonialism, that we should risk the displeasure of France in making this clear to the Chinese? Well, I think we've got to be tactful, of course, the French are our friends. But this is to the interest of the French too. I think deep in their hearts the French know this just as we all know it. Certainly they all say it off the record. Well, what about the second part of the revolution in Asia, the revolution against feudalism? How can we advance that in Indochina? Well, now, for instance, in Asia, many of these Asian countries, the governments are doing really very little to help themselves. I won't say many, but some. For instance, the tax systems are falling on the poor people. The wealthy people pay either very small tax or no tax. The land is owned by wealthy landlords. They take 60 or 70% of the crop. The peasants work in the hot sun day after day after day and get very little out of it. Now, I can see no reason for us to give aid to any country that is not willing to put its own house in order, is not willing to make its own effort to try to build up the future of its people. That's the first position I think we should take. You mean that we should insist on land reform and on high income taxes in these nations before we extend loans to them? Well, put it this way. If a friend came to you and said, I want to borrow some money, the first thing you'd say is, well, are you ready to work? Are you going to get to bed early at night instead of going out playing poker and running around generally? Are you going to really work hard at this job and save your money? If you are, I'll help you. You're willing then to attach strings to American economic aid? I certainly am economic strings, not political strings. I think with any non-communist country, you have to be very careful not to tell them what their foreign policy is or try to control them politically. They'll resent that just as we would resent it. In the Philippines, didn't we attempt to attach some strings or something? Well, we did attach economic strings. And we said it through the Bell report that we would give no money to the Philippines unless they put through a decent income tax that fell on the people who could afford to pay land reforms and control of luxuries. We did this, some of the reforms went through, the rest didn't. But the people of the Philippines know that we are their friends. They know in their hearts on the streets of Manila and in the villages. Well, we succeeded in pressuring the Philippines to institute reforms, land reform taxation. Could we do the same thing in India, in Pakistan, the more important countries? Well, in India, I don't think you have the problem. India is taxing her people very heavily. She's controlling her luxury imports. She's putting through land reforms, not as fast as I think she should in some parts of India, but I would say half of India, the reforms have gone through. And the government and the people there are carrying a very heavy burden. They're taxing themselves heavily. What countries need this pressure from us to effect reforms? Well, now you know, I've been just a diplomat for the last two years. You're getting me into some embarrassing ground here. But let me say I can think of two countries at least that could stand this treatment. And I think that if we applaud it, we win the respect of the people of those countries and also the people generally of Asia. Just one question about Indochina. If we tell the French that we're going to help throw them out of Indochina, at the same time, we'd have to ask the French to effect reforms in Indochina while they're still the government. Can we do both of those things at once? Well, at least I'd try. At least I'd let the people know where we stand. Let me tell you a little story. Well, as I'm afraid, our time is getting a little short, Mr. Bowles. I want you to make this other point. And that's this point about the racial revolution. Now, what positive step can we take in that direction? Well, the first thing we have to do is really accept the Asian as a human being, not as a mysterious and inscrutable and faraway sort of person that we're not, we can't understand, but a decent human being. Now, I think I know the Asians pretty well. I've lived there the better part of two years. I've known them intimately and well. And they're wonderful people. There are kind of people. I think we're their kind of people. We should send people to Asia. This applies to business firms. It applies to the State Department. It applies to all of us who are willing to work with the Asians. Except their viewpoint, listen to what they say. Well, that's a final question, sir. What do you regard from all of this as the most important action that America could take in Asia today? I think the biggest thing America can do is get over her fears. I've come back to America and I find her frightened and frustrated. We're talking in negative terms. We're talking against communism, anti-communism, negative communism, against communism. Of course we're all against it. But we can't defeat communism or any other kind of force without believing in something very deeply. We built this country on faith. We built it because we believe deeply in certain things. That's the way Asia is going to become free. And that's the greatest force in the world. The confidence and faith of free people. Well, I'm sure that our viewers have very much appreciated these statements of yours, sir, and thank you for being with us. The opinions that you've heard our speakers express tonight have been entirely their own. Our distinguished guest for this evening was the Honorable Chester Bowles, former United States Ambassador to India. At the end of this week, after two full years on the CBS television network, during which you've witnessed some 275 presentations, the launching chronoscope will begin a vacation for the summer. Now we wish to express our thanks to our senior editor, Mr. William Bradford Huey, and to all those on stage and backstage who've worked so hard and so faithfully in our behalf, including our associate editor for this evening, Mr. Elliot Haynes. The world honors which Lone Gene Watchmakers have won represent the considered opinion of impartial, qualified experts on the high quality maintained by Lone Gene Watchmakers over the years. These Lone Gene honors, which include 10 World's Fair Grand Prizes and 28 Gold Medals, and highest honors for accuracy from the great government observatories are a tribute to the elegance and beauty of Lone Gene Watches, as well as to their excellence and dependability as timepieces. In these Lone Gene Watches of today are found in perfect harmony, the art and craftsmanship of master jewelers, and the science and skill of master watchmakers. Now, should you wish to buy for yourself, or as an important gift, just about the finest watch made anywhere in the world, you do well to choose a Lone Gene.  Lone Gene, the world's most honored watch, the world's most honored gift, premier product of the Lone Gene Whitney Watch Company, since 1866, maker of watches of the highest character. The Lone Gene Chronoscope, a television journal of important issues of the hour, is broadcast on behalf of Lone Gene, the world's most honored watch, and Wipnore, distinguished companion watch to the world honored Lone Gene. This is Frank Knight, reminding you that Lone Gene and Wipnore Watches are sold in service from coast to coast for more than 4,000 leading jewelers who proudly display this emblem, Agency for Lone Gene Wipnore Watches. There's Sunday daytime adventure on the CBS television network.


You have no pure capitalist state at the moment to Bemidithwyr, to defyde y Llywodraeth, to conclude the one party systems. Do you think these ideas you are speaking about, the result of the state has become... Do you think capitalism has developed and hasban them? Do you think these ideas you are speaking about, the result of the state has become... The ideas you are listening about is the result of the state's income. Are there two party systems that you have to have to have to be released? Or you have to have a multiparty system and it doesn't exist anywhere now? Yes, I mean... Note the essence... This is not the multi-party system the essence is... is that the Founding Fathers of US didn't believe that the existing party ought to be party It said that everyone should run as an individual and there should be no party in this sense advice that could be outcome If it didn't succeed they recruited parties very very quickly. I think if you define the role of government closing dyna i'n credu sut y dyna'n ysgolwch arall, ti'n raddau yr wych erioed i'r gwahyd ac yn ni wneud dyfodol, ac yn cyfodol gweithio, ond ystafell, y constitution americ yw'r dim yn ei amgylchedd fel y ddechrau yn ôl yn gweithio, dweud â'r amlwn, felly mae'n ei Dimwil ychydig iawn i ddechreu. Rydych chi'n mynd i ei bod y bydd agorod o eraill i'r pethau cyfnod a beth o'r internet? Felly yn dd Codei A chest oherwydd, Rydym eich cyfnod, ddawer Iedwg yma, ac yna fod yn ydyn nhw'n sydd wedi'i ddisgu bod y bod y dyma yn unig ymwowodd am y cyfnod i'r Gwyrdd Ddweud yn y Llywodraeth. A'r cyfnod yna eich cyfnod dosesfod. A dwi'n cael i'n mynd i'r prifативu bod gyda'r cyfnod communications a byw am ffog i'r Llywodraeth ar y cyfnod yn yw amfer. Felly oedd yna rhoi bobl o'r clwrs? No. Dwi'n credu go llawer. I don't think politicians will be that interesting of a profession, or that important of a profession, because I think that the government will do very little. You know, maybe it only needs to be, you know, Congress only needs to meet three months a year. Probably doesn't need 12 months because what do they do? There's not much to do. I think to this day the legislature in Texas only needs every other year. They don't even meet all the time. Texas is probably the fris of the states, among the fris of the states in the United States. So you get part-time politicians, you know, a working man who do this in addition to their regular jobs. You get robust debates about real issues, about applying the concept of individual rights. You probably get some multi-party system, and maybe not, maybe without the individuals. I don't know how it will all play out. The essence of stability is two things. Getting a constitution right, unambiguous and right. And second, having a culture in which that constitution, that people believe in that constitution. So you can have the best constitution in the world, and if people don't believe in it, it's your own. So the United States is a pretty good constitution, probably the best in the world. Not perfect, but really, really good. But people stop believing in it, 100 years ago. And our schools stopped educating about it 100 years ago. And the ethics that are prevalent in the culture is anti-daf, so the constitution. So what's happened? The constitution is slowly being checked away and eroded at, and the screen quote keeps you willing to guess what the true nature of the constitution is, because they don't understand it, because they've lost the intellectual path back to what the constitution really meant. So you need, philosophically, a culture that believes, continues to believe, that that constitution that system of government is right in order for it to sustain itself.