 Hello, everyone. This is the Circuit Python Weekly for August 9th, 2021. This is the time of the week where we get together to talk about all things Circuit Python. I'm Scott, and I'm sponsored by Adafruit to work on Circuit Python. Circuit Python is a version of Python designed to run on tiny computers called microcontrollers. Circuit Python development is primarily sponsored by Adafruit, so if you want to support them in Circuit Python, consider purchasing hardware from Adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join any time by going to the URL adafru.it-discord. We hold the meeting in the Circuit Python Dev Text Channel and the Circuit Python Voice Channel. This meeting typically happens on Mondays at 2 p.m. Eastern Time, 11 a.m. Pacific, except when it coincides with the U.S. holiday. If the meeting time has changed, we'll notify you via Discord. If you wish to be notified about changes to the meeting, we can add you to the at-CircuitPythonNesis Discord role. That's the one that Will mentioned. And there is also a calendar available that we try to keep updated if you'd like to subscribe to that. This meeting is recorded. We record the audio of the voice channel, the video of the text channel. If you would rather not have your voice recorded, you are still welcome to participate. The video of this meeting will be posted on the Adafruit YouTube channel at youtube.com. And the audio is released as a podcast. If you find this podcast is not available in your favorite podcast service, let us know. There is a notes doc to accompany the meeting and recording. If you wish to participate but can't make it to the meeting, you can leave hug reports and status updates for us in the document. We'll read them off during the meeting. The notes document also contains timestamps to go along with the video so you can use the doc to view only the parts of the video that interest you most. The meeting tends to run 60 to 90 minutes, so this gives you the option to skip around. A link to the notes document is posted in the hashtag circuitpythondev channel on the Adafruit Discord every week. Check the pinned messages to find the latest notes doc. This meeting is held in five parts. The first is community news. This is a look at all things circuitpython and python on hardware in the community. It's a preview of the python on microcontrollers newsletter. The second part is the state of circuitpython libraries in Blinka. This is a statistical overview of the entire project. And 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 the opportunity to highlight the good things folks are doing, taking the time to recognize the awesome folks in our community. This is a counter to bug reports. The fourth part is status updates. Status updates is an opportunity to sync up with what we'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. The fifth part and final part is in the weeds. In the weeds is an opportunity for more long form discussions. These discussions can come out of status updates or be something you've identified ahead of time is too long for status updates. And that covers how the meeting will go. And with that, I will switch over to the note stock and start with community news. So community news is a preview of the python for microcontrollers newsletter. And first up, we have an article about the Raspberry Pi rolls out new documentation online until recently documentation for the non Pico Raspberry Pi boards was on GitHub and get in GitHub Markdown language. As of Monday today, a new documentation site Raspberry Pi org slash documentation has been built and deployed directly from the repository, which is github.com slash Raspberry Pi slash documentation using GitHub actions. When someone pushes to the master branch, however, people will will mostly be working out of the develop branch in the repository, which is the default branch when you take a fresh checkout. And also the branch you should target for your poll requests. And there's more information on the Raspberry Pi blog. Next up, there's now a new notable women business owners 2021 with its list of notable women business owners cranes recognizes those who have forged their career paths and then turned power New York City's economy. Women owned companies represent more than 40% of all registered businesses in the city and generate more than 70 billion in revenue annually. More freed founder and engineer at Adafruit Industries was selected among 63 recognized women among 66 or our site, 600,000 women of businesses in New York and the link there to cranes New York business. Next up is a circuit python day 2021 recap circuit python day 2021 was held Friday, August 6th with events leading up to the big day. Thanks to all the who contributed to make this year a rousing success. Here's a list of events you can watch on YouTube covering the discussions. First is show and tell from Wednesday. Next is Tim, aka foamy guys circuit python day broadcast. And then a Jeff Dan and Catney discuss circuit python. Lady aided did a circuit python board tour. And I did a circuit python deep dive. That's the roundup and missing on that is the Reddit AMA as well. We should get that on there. And we'll add that later. Next up the chip shortage challenges maker manufacturers. Two resources discuss the effects of the chip shortage. First chip shortage challenges maker manufacturers ate a fruit spark fund and other wellsprings of amateur innovation face a new normal. This is from IEEE spectrum. And then there's also a YouTube video called why there are now so many shortage in parentheses. It's not COVID. And thanks to foamy guy for dropping the notes in there. And thank you to Jeff for the link to the AMA as well. Next up. Python and visual studio code. The August 2021 release. The August 2021 release of the Python extension. For a visual studio code is now available. This includes a revamped Jupyter notebooks experience brought by the Jupyter extension now out of preview and it an improved way of sorting Python interpreters in the selection list. There's a link to the Microsoft Python dev blog. Next up is the state of Python in 2021. It's a review of many things happening in Python this year. It includes several sections. And this is from D programic program. Matica. I think that's what it is. And the sections are the ecosystem, machine learning and scientific computing, getting Python, learning Python, Guido van Rossum and more. Next up. We have the real Python podcast with Nina Zacharenko. The real Python podcast hosts Python East and Nina Zacharenko. The topic is start using a debugger with your Python code. And there's a link there. And that is it for the community news for this week. If you would like to know more or get subscribed to it, the circuit Python weekly newsletter is a circuit Python community run newsletter emailed every Tuesday. The complete archives are available at www.aiderfruitdaily.com. It highlights the latest Python on hardware related news from around the web, including circuit Python and Twitter. To contribute your own news or project, edit next week's draft on GitHub, go to github.com. Check out the drafts page there. And submit a poll request with the changes. You may also tag a tweet with hashtag circuit Python on Twitter or email cpnews.aiderfruit.com. And, yeah, I butchered the name of that website. Okay. Let's move on to the second section of the day, which is the state of circuit Python libraries in Blinka. This is a statistical overview of the health of the project meant to ground us in the numbers before we talk about how we feel about how things are going. First up, the overall numbers. Overall, we had 23 poll requests merged from 14 different authors. So thank you to all of our authors. Some new folks that I don't recognize is our Pavlik, our Dorsanod. So thank you to those new authors. We had seven reviewers. So thank you to our reviewers. As always, we couldn't have as many authors as we have without other reviewers. So thank you, everyone. Issues-wise, we had 24 closed issues by nine people opened by 13 people. So we are down nine, which is great. And as we can see by the number of people involved, we are growing. We're starting to hit the double digits, which is exciting. All right. Now for the core. We had 15 poll requests merged from 11 different authors. So thank you to all of our authors on the core. We had four reviewers. We have 13 open poll requests, but the oldest open is now 16 days. The one that was previously open over 100 days was a bored one, and we've since had, and I think merged a newer version of that, but we had to close the old one. So thanks to folks for doing that. And it's super exciting to see our oldest poll request at only 16 days old. That's really awesome. Issues-wise, in the core, we have 16 closed issues by five people and six opened by five people. So we are net down 10, which is awesome for a total of 433 open issues. The way that we track and keep track of our issues to make sure that we're at least triaging them is by using milestones. We have two issues currently not assigned to milestone. These are the ones that we need to triage. And then we have 29 open issues for the 700 milestone, which is our goal to fix things for the stable release. So that is kind of the where all a lot of the action is happening right now is on the 700 milestone. And with that overall, expect to see another pre-release this week. And it may be an alpha or a beta depending on whether we've kind of wrapped up all of the API changes. But please keep testing it. And if you find things that you think are urgent enough or important enough to do for 7.0, please mark them as 7.0 or suggest that we do that. Otherwise, we'll keep pushing to get 7.0 out the door. It's got a lot of really good stuff, so it's time. And with that, let me kick it over to Katnney for the libraries. Thanks, Scott. So this applies to all of the Adafruit circuit Python libraries, which is everything that begins with Adafruit underscore circuit Python underscore, as well as the community bundle, the Adafruit circuit Python bundle, and our cookie cutter. So few extra fun ones in there as well. So across all of that, we had eight pull requests merged this week by five different authors and six different reviewers. We had, that loses with 45 open pull requests. We had eight issues closed by six people and eight opened by seven people, so we are not even with 332 open issues. If you're interested in contributing to circuit Python on the Python side of things, check out circuitpython.org slash contributing. You'll find all of this information and more all of the open pull requests, all of the open issues and some library infrastructure issues. You can search the issues by label. So if we need to get better with curating our good first issues, but you can check out bug or enhancement if you're looking for something a little more complicated. But find something that interests you and leave a comment on it and let us know what you'd like to work on it. In terms of reviewing, take a look at the PRs. If you have the hardware, test it. If you don't, you can check it for syntax or spelling or style type things and make suggestions, leave a comment. And once you're comfortable with that, we can talk about leveling you up and there is a guide on contributing to circuit Python using Git and GitHub. So don't let that intimidate you and we're always available to answer questions. We want you to be able to contribute in the way that works for you. So in terms of library updates in the last seven days, we've had one new library. It's the IS31FL3741. Can't believe I made it through that. And we have a few updated libraries that I will not read off. Overall, we're continuing to see work to both the Adafruit and community bundles. And I want to say early, thank you to everyone who's been handling the breaking changes fixes, especially FOMI guy and Lysanmar appropriate. That's what I've got. Awesome. Thank you, Katnie. And next up, let's go to Melissa for a Blinka update. Hello. So Blinka is our circuit Python compatibility layer for MicroPython and Raspberry Pi and other single board computers. And this week, we didn't have much activity. We had zero pull requests merged. There are currently two open pull requests and there were zero closed issues by zero people and one open by one person. There are currently 60 open issues. There were 9,844 PiWheels downloads in the last month and we are still currently supporting 75 boards. And that's it. Awesome. Thank you, Melissa. All right. And that's it for the Stadia Circuit Python libraries in Blinka. Next up, we have Hug Reports. Hug Reports is a chance for us to say thank you to the folks in our community who are doing awesome things. This is done as a round robin, so I will start and then go down the list of folks in the note stock. If you're just listening in and not participating, then just don't list yourself in the note stock. But if you do want to participate, feel free to drop your notes in the note stock. If you're not able to make the meeting, if you're listening to this after the fact and would like to participate in Hug Reports, you can go to the Circuit Python dev channel, check the pin messages, and add your notes to the note stock and I'll read them off for you. So let's get started. First up from me is a Hug Reports DCD for taking time codes through my stream. Thanks to Keith the EE for hosting our Reddit AMA. Last week it was really fun. Hug Report to Katnie, Dan, and Jeff for the Circuit Python Day stream. I watched it and enjoyed listening to you all answer questions and show off your projects. Very cool. And then lastly, Hug Reports Dave P for testing my CMD-21 ticks change. Timekeeping on the 21 is really hard and so Dave's done some really good work and I was happy to have Dave's eyes on the changes that I made. I'll have to keep looking at that. And with that, let me circle around and read off Ann's notes. So Ann says, Hug Reports, or thanks to all who made Circuit Python Day and Circuit Python Week so wonderful, especially FOMI guy, Katnie, Dan, Jeffler, and myself. Next up from, do we want to go to Charles? Is that reading it off? Charles isn't jumping in so I'll say Charles has a group hug. And next up we'll go to Dan. Hello. Thank you, Jeff and Katnie. We did a stream together on Circuit Python Day. That was a lot of fun demonstrating things and just answering questions. Worked out very well. Very nice experience. Thanks to Keith, the EE who set up a really excellent Ask Me Anything for Circuit Python and Migrapython on Reddit on the Python subreddit. There were some extremely thoughtful answers, especially by Jimmo, about aspects of MicroPython and Circuit Python and the differences and various features and stuff. It's a very worth reading. And thanks to Nathan by 3G who, for their first PR, was to add board.led to Grand Central, which was something that I had meant to do in this massive cleanup of board.led and still missed. Okay, thank you. Thanks, Dan. Next up I have notes from Dave P. Dave says, Hug reports Dan H for putting me in touch with a cousin who contacted him for macropad help. I had not had contact with him for many years. And next up is Foamy Guy. All right, thanks, Scott. First up, hug report for Niradoc for starting up a repository to hold alternative keyboard layouts. So that's been a project that's been in the works for a bit. Niradoc got the ball rolling pretty well on that. To Ann and anybody else that was involved in organizing the festivities for Circuit Python Day to all the folks that streamed with me, Jeff, Dan, Lady Aida, and you, Scott, appreciated all of those streams, to Warrior of Wire for helping me out quite a bit on some core code, pointing me to some examples that turned out to be super helpful, and likewise to Jeff and Dan who helped me out as well and pointed me to some great concepts that I need to study up on. And lastly to community member Gary Z who made a really neat arc gauge widget for display IO. So that's been really neat to play with. And that's it for me. Thank you. Thanks, Fovey Guy. All right, next up is Jepler. Hello, I need to dig my notes out because I was reading Niradoc's keyboard layout repo and I'm happy to see that arrive. So hug report to them. Also to Ketney and Dan for the YouTube live broadcast on Friday, it's not quite the same as hanging out with friends, but it's a lot like hanging out with friends. So that was nice. Made it a lot more fun too. And thanks to everyone else who participated in Circuit Python Day, whether that was as a broadcaster or just as a listener. Another thanks to Niradoc and then Fovey Guy for quick feedback on something I implemented on the weekend. Circuit install dash dash auto, which I'll mention down in my status update. Awesome. Thanks, Jeff. All right. Next up is Jerry. Hi. Yeah, thanks to Jeff for the OB2640 webcam guide. Had a lot of fun with that. And the QR code reader module also fun to play with. And yeah, hugged everybody involved in the Circuit Python Day streams. Thanks. Thanks, Jerry. All right. Next up is Ketney. So let's see. I have a lot of important hug reports. So I will not say first and foremost today. So first up anyway, Mr. Certainly for tracking the questions and the various chats outside of discord on our Friday live stream so that we could focus on streaming and only have to track discord to answer questions. This was unbelievably helpful and greatly appreciated. Thank you to Keith, the E for organizing the Circuit Python Day circuit Python, micro Python red at AMA. That was excellent. Thanks to Jeff and Dan for an excellent stream on Circuit Python Day. And thanks to everyone who participated in Circuit Python Day to echo Jeff, who said everybody who was streamed and everybody who didn't. Our stream ended up going for a solid two hours and over an hour of that was just answering questions from folks who were asking questions all over the web. So that was great. Hug reports to warrior of wire and phony guy for working on fixing vector IO issues to Jeff for helping me automate renaming some files and get even though we went through a broken version and a couple of iterations before getting it right, it's still better than how I was going to do it. And finally, a Pendly on GitHub for their first contribution to a Circuit Python library. A new example for the macro is what they submitted and they stuck through getting through CI failures, getting things set up locally to handle the failures and persisted through getting it passing. So I wanted to give them a nice hard report for that and look forward to seeing more of their contributions in the future. And that's what I've got. Awesome. Thank you, Katny. All right. Next up is Keith E. Hi. I wanted to say first hug to you, Scott for helping organize the Ask Me Anything thread that we had on Reddit. Thanks to you that I was able to get in touch with everyone and bring in MicroPython alongside Circuit Python for the AMA. And that made it really special to me. Thanks to Katny, Phillip, Jeff and Phomy Guy for helping with announcements throughout the week and throughout their streams on Friday. Dan, because as soon as he saw a question way before the scheduled AMA was ready to start, he jumped in and helped someone and answered their question. Scott and Jim from MicroPython because their answers were super thorough and they built off each other's answers. So I got a really neat perspective of the MicroPython approach and Neridoc they jumped in on a question they had a fantastic answer to and to the community as a whole and everyone involved in Circuit Python Day for making it a really cool experience. Thank you. Thanks, Keith. All right. Next up is Melissa. Hello. I wanted to start off with giving a hug to Dan for the great guide on customizing Circuit Python. Everyone who participated in Circuit Python Day and group had different else. Awesome. Thanks, Melissa. Next up, we have notes from Neridoc who says hug report to Jeffleer Jeffleer and Micronev for the traceback module hug report to Jeffleer for the CircuitPy...Circup install dash dash auto Jeff says he answers to Jeffleer. I'll go over to Jimmo myself, Dan, and everyone else who participated in the Reddit AMA and a group hug for the community and all those I forgot since I don't do that very often. Thanks, Neridoc. All right. Next up is Status Updates. Status Updates is done just in a similar way as around Robin. But this time we're talking about a little bit about what we've been working on in the past week and what we're doing in the coming week. It's a way for people to stay in sync and give tips or tricks to other people if they're working on stuff that we may have worked on in the past. So I will start and we'll go around just like we just did. So first for me I've been working on more fixes. I finally got my GDB Happy again thanks to help from Dan and the problem was actually the linker, so the linker got fixed and that's been making things happier which has been nice to be able to be in my GDB Happy Place again. So I'm working on the fix for the reload while doing Pulse In. I talked about that earlier working with Dave so I'm going to take a look at the DHT this week and see if I can't figure out why we're losing accuracy still. And then I'm going to look at more issues to fix to get 7-0 out the door so we still have 29 at least so and Dan pointed me to a similar one with the Sandy thing so I'll take a look at that as well. So yeah lots of bug fixes this week for me I did PR last week the Adafruit Beely UUIDs to the Nordic Numbers Database which I believe powers the NRF Connect app in terms of like having friendlier names for the UUIDs that it sees so that should be helpful in the longer run. And then some other folks are still working on the really workflow apps and I will be checking with them and making sure that we're making progress and if they find any bugs on the device side I'll make sure and tackle those as well but I am not a strong client side person so I will have to kind of rely on those folks to push those forward so that's where I'm at doing a lot of odds and ends. Next up we have Notes from Warrior of Wire who says tons of fixes simplifications ergonomic features and performance improvements in Vector I.O and no more vector shape so trying to get some API changes in for 7 as well and circling around we have Notes from Ann who says please keep sending news, projects and tips to cpnews.atafruit.com The summer we've noticed with these meetings being a lot quicker tend to be a lot less busy because folks are busy and taking vacation and stuff so that applies to that applies to the newsletter as well so if you know of cool projects that people are doing with Python, MicroPython, CircuitPython please email cpnews.atafruit.com and we'll get those out at the door in the newsletter and highlight the cool things that people are doing and with that let's go to Dan for his status update. Okay mostly I've been working on audio debugging which is I've spent several weeks on but I keep getting narrowing it down and finding more clues the latest thing I've found is that for some reason the sample rate of the audio that I'm trying to play makes a big difference even though it shouldn't because it's not sample rate only affects a few calculations so I have to look at that in more detail what I'm trying to fix is crackling and sometimes the play stops completely on something like the macro pad where other things are happening with memory access especially with DMA like the display or other things happening at the same time that are significant background tasks it's not necessarily that the other thing is DMA just that it's happening but it seems to be more common when the other thing is DMA and I've done a bunch of instrumentation like flipping pins when certain things happened and I can look at that output on a CLA and then look at the timing of things because I'm looking at things that are pretty timing critical and if I put in print statements but only I tend to put them in when the play is complete I might put them in the middle but it tends to affect the outcome of what I'm trying to debug just to make sure that you know our both channels busy at the same time why is that happening that shouldn't happen okay that's it for now thanks for this thing on that Dan alright next up is foaming game alright last week I worked on we wrapped up the remaining max size and on disk bitmap updates and the learn guides with a bunch of help from LaysamuraiPourPay so thank you I worked on some enhancements for the grid layout one to look up the contents by their XY cell position instead of having to know the index that they were added like the order they were added in and another one to add divider lines between the cells and I worked on helping to make the gauge widget that Gary Z created so that it can redraw itself when a new progress gets set instead of making a new one and adding it to the group again for this week I'm going to start looking into the PWM out and the other few remaining breaking change fixes so things that will need to get changed for your circuit python 7 I'm going to work on adapting an older dial widget to use the new vectorio API I think that's the only place where vectorio is in use so far so we're going to update that to work with the new API I'm going to hopefully finish up the divider line functionality in grid layout and get a PR submitted for it I'm going to try to clean up some code in the core that I've been working on and get a PR submitted for that it's to make a boundary fill function that will kind of do like a paint bucket style fill that's going to help speed up drawing some different things and then lastly I'm going to try out some other ideas I have to try to make that gauge draw a little bit faster and also get a repo set up for it with cookie cutter so that's what I got going on this week, thank you thanks foamy guy alright next up is jet player gotta find that unmute button so last week the main thing was a new guide on the learn system about uploading camera images to ate a fruit IO so check that out and always happy to have feedback from Jerry which I didn't mention in hug reports about that I implemented a new feature in circup you can now say well once it's released and merged you'll be able to say circup install dash dash auto and it will do the same thing that bundle fly does which is open up your code.py send it to find import which will list out the libraries you need so kind of a one-step hopefully to get the files you need onto your device I implemented a module called qrio for scanning qr codes and it was really easy thanks to a C library that I could use called quirk and I pull requested some random bug fixes into circup python midi I saw some activity there over the weekend a person's see I was failing but not due to their bug due to some other stuff and I thought well I can do a little tidying up here so anyway this week the focus is to create a guide on scanning qr codes and one will do it just simple well at least two examples one will do it simple just into the repel and the other will upload the qr code to Adafruit IO since we're doing Adafruit IO right now and it seems like based on memory problems that Jerry is going to mention probably you'll need to stick with the psp32 modules with psram for doing qr codes so that's kind of a bummer anyway and then plenty of miscellaneous you can stalk me on github and look at my github activity if you want to know more about what I've been up to which is exactly how I make these lists anyway thank you thanks Jeff next up is Jerry yeah so yes I played around with the qr code reader stuff that was a lot of fun and it worked really well on the kaluga and so I got the brilliant idea I'll just port this over to apico and it ran out of RAM pretty severely forgotten about the fact that the rover module has that big psram so I guess we'll not stick with that and then I thought what I'd like to do though and I don't think there's any reason why this shouldn't work is to convert the webcam demo over to the seola rover because it'd be a nice smaller package than the big kaluga since you don't need to necessarily have a display for that so I'll try and get that done this way you can see it works and then for fun I finally took the big step and got myself a 3D printer and got my first test print underway and so all of my spare time for the next six months is committed awesome looks cool jay yeah thanks next up is catney at least jerry understands the loss of time that comes with a 3D printer alright so I scrambled this together at the last minute and actually it ended up being huge so last week I updated the pcf 8235 and the deus 3231 guides to include the stem acute versions normally we replace products with the stem acute versions but in this case the originals are super still used by folks so they're new products and the guides are written to include both not to have one be a replacement so that's what's going on there we will eventually suggest folks start using the stem acute version but that'll be a slow change those are both real-time clocks by the way so there are now stem acute real-time clocks which are super convenient for example adding to your micro pad so I did some significant template cleanup involving moving code around to be bundle flag compatible also so it generates the dynamic circuit pipe content screenshot images updated some of the templates to use the dynamic images updated all the related links to the moved code updated examples to use rainbow so it's a single example in the template instead of a separate example for every guy using the template then I finalized the code side of my macro pad shortcuts example but I'm still thinking about what I want the shortcuts to be specifically I am open to suggestions it is a github text expander setup where it's common phrases used on github such as the LG M key sends looks good to me and the TFYC key sends thanks for your contribution what common phrases do you send in github issues and PRs let me know if you have any that are common to you or things that you see a lot that you think would be useful I created a PR to the learning system guides repository renaming all instances of main.py to code.py to prepare for updating the associated guides the PR is not yet merged as it will break over 30 guides and I'm waiting until I have Dylan's help to update the guides once we merge the PR and I hosted a chat on Friday we went through the full two hours because of all the amazing participation by the community asking questions and so on and thanks again to Bruce for the assistance with tracking the various chat avenues this week I ordered up the MCP 9601 so I can do the guide for that it's very similar to the old version but not similar enough to be included in the existing guide so it will get a new guide depending on Dylan's availability possibly do that main.py to code.py rename and learn otherwise it's not a rush the PR is in it's fine whenever we're ready to do it continue to think about what I want my macropad project shortcuts to be and eventually the plan is to do a guide on that one I'm going to potentially do a Neo key trinky guide specifically for sending time stamps from OBS into a document for keeping time stamps in notes during live streams or recordings and then various miscellaneous this is where it's sort of petered out because the meeting started and I needed to get back to earlier in the notes and then more template stuff once I get through all of that and or run out of other things to do and that's where I'm at. Awesome thank you Katni Alright next up is maker Melissa Hello so last week I was out sick much of the week fortunately I wasn't COVID but I still felt awful I worked on the macropad guide and finished up some code and started actually I finished up my coding on that and started writing up the guide so we can finish up my guide and possibly start another one and other stuff is I'm moving all my stuff into a new office to make room in my home and not having to constantly reconfigure everything and that's it. That's exciting I think that's something I'm going to do at some point too Yeah it's like you realize it's like it's kind of cramped in here and if you're trying to do multiple things and you're here you have to reconfigure everything Yup that's cool though Alright thanks Melissa and if you have cycles please let me know because I'd love your help with the code.circuitbython.work Okay yeah Actually I might have cycles after this guy's finished up Okay yeah just let me know I'd love to see some more work done on that but you have the skills that I do not have Thanks And that's it for status updates. Lastly we have In the Weeds In the weeds is a section where we just talk kind of whatever is on our minds Typically we have folks drop notes in the In the weeds section and we do have one topic here so hopefully Warrior of Wire is ready to talk in the weeds here Yeah so Katny requested in the chat kind of a status update on vector IO so there are breaking changes with the API in vector IO that I'm hoping to get in for 7.0 the 7.0 release of CircuitPython They are simplifications so now you can just like add rectangles and circles and polygons directly to your display groups instead of having to like proxy them through a vector shape that doesn't exist anymore you can just declare a rectangle of whatever color and just like throw it into your display group There are a just litany of issues that are fixed in the pull request that's out in vector IO It should be a lot more user friendly and actually work like the rest of display IO with these changes so I would recommend that any integration with vector IO be done against the pull request version because it like correctly handles things like display rotation if you install the screen you know rotated 90 degrees like a lot of my projects are Yeah but as far as the PR goes like it passes all the CI tests and everything just awaiting final sign off and getting ship I think FOMI guy tested it as well so there's confirmation from at least two people that it works on circuit python devices Okay so Go ahead I mean if you want me to test it as well I can otherwise it seems like it might be ready to go Sounds good to me Okay I'll handle that then and yeah the rotation is how I found it I was absolutely convinced that vector IO didn't work like I thought it should and it was the rotation problem it was not vector IO did work exactly like I managed to figure out it's just that the rotation didn't work and this project has the macro pad rotated 90 degrees Well warrior wire thank you for jumping back into this Yeah it's the way it should have been all along so thank you for your patience Absolutely so I will handle getting that merged then and then that we in the next circuit python 7 release Awesome thank you Thank you so much for the update this is much clearer it was hard to follow the whole conversation obviously Yeah so this was excellent thank you very much for taking the time to explain and we'll get that taken care of Cool thanks that's all I have Awesome and that's it for in the weeds so now I will wrap us up this has been the circuit python weekly meeting for August 9th 2021 I'm going to scroll down to the bottom of this dock that tells me what to say Thank you to everyone who participated if you want to support Adafruit circuit python those of us that work on circuit python consider purchasing from the Adafruit shop at Adafruit.com the video 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 which you can sign up by going to AdafruitDaily.com and check the python for microcontrollers newsletter box there it is a separate site because it is a separate list from the Adafruit.com stuff so it's just for the newsletters that's all you'll get by signing up here and the next meeting will be pull up my calendar next Monday the 16th at our normal time which is 2pm pacific 11am wait 2pm eastern 11am pacific that's what I get for talking and switching browser tabs at the same time this meeting is held on the Adafruit discord server which everyone can join by going to the URL adafru.it slash discord to be notified about the meeting and speak in the meeting you can ask to be added to the at circuit python role on discord and with that we hope to see you all next week thanks to everybody for taking the time hope you have a great week and we'll see you on the discord thanks everyone