WEBVTT 00:00:00.040 --> 00:00:06.240 Hello and welcome to Python Bytes, where we deliver news and headlines directly to your earbuds. 00:00:06.370 --> 00:00:12.000 This is episode 454, recorded October 20th, 2025. I'm Michael Kennedy. 00:00:12.390 --> 00:00:13.160 And I'm Brian Okken. 00:00:13.500 --> 00:00:18.740 And this episode is brought to you by us. We have increasingly more monotonically increasing 00:00:19.180 --> 00:00:23.020 number of ways in which you can support us and things that Brian and I both feel like 00:00:23.400 --> 00:00:26.640 contribute a lot of value, right? Your pytest book, your pytest courses, 00:00:27.400 --> 00:00:29.180 All the courses over at Talk Python, 00:00:29.739 --> 00:00:32.160 foreshadowing, some of that's coming later as well. 00:00:33.040 --> 00:00:33.800 The Patreon supporters, 00:00:35.440 --> 00:00:36.320 pretty much all of these things. 00:00:36.500 --> 00:00:38.800 We create them not just so that we have a job, 00:00:39.040 --> 00:00:41.000 but also because we think the world needs them. 00:00:41.240 --> 00:00:43.460 We appreciate when you all agree with that and support them. 00:00:43.640 --> 00:00:45.620 You want to connect with us, connect on social media 00:00:46.180 --> 00:00:47.720 or on most of the social media. 00:00:47.820 --> 00:00:49.940 There's the links at the top of the show notes. 00:00:50.300 --> 00:00:54.480 Join us live right now, Monday, just after 10 o'clock. 00:00:54.720 --> 00:00:56.040 Typically, it's when we start live streaming, 00:00:56.520 --> 00:00:57.540 although sometimes it varies. 00:00:57.860 --> 00:00:59.580 So subscribe to the YouTube channel 00:00:59.880 --> 00:01:03.180 and get notified there to make sure you get all the notifications. 00:01:03.380 --> 00:01:05.059 But typically we aim for Monday at 10 00:01:05.379 --> 00:01:06.780 until further notice at least. 00:01:07.180 --> 00:01:08.520 And finally, subscribe to the newsletter. 00:01:09.240 --> 00:01:10.940 We're putting a lot of effort into sharing 00:01:11.160 --> 00:01:14.020 a really nice, rich, extra bits of information 00:01:14.300 --> 00:01:15.660 out to the newsletter there every week. 00:01:15.980 --> 00:01:17.700 So appreciate that going out. 00:01:18.120 --> 00:01:18.840 And I think it's been, 00:01:19.440 --> 00:01:20.620 we put a lot of work into this, Brian. 00:01:20.620 --> 00:01:21.200 I mean, a lot. 00:01:21.440 --> 00:01:22.600 So I'm ready for a rest. 00:01:22.900 --> 00:01:23.800 Take a little rest. 00:01:23.920 --> 00:01:24.200 How about you? 00:01:24.520 --> 00:01:25.080 Yeah, yeah. 00:01:25.180 --> 00:01:26.120 We should take a rest. 00:01:26.300 --> 00:01:27.620 maybe with a REST framework. 00:01:27.860 --> 00:01:30.140 Oh, because sometimes you need a whole framework to REST. 00:01:30.140 --> 00:01:30.600 You're that tired. 00:01:31.300 --> 00:01:33.620 Yeah, so let's pop this up. 00:01:33.810 --> 00:01:35.800 So we've got an article. 00:01:36.320 --> 00:01:37.920 This is sort of going backwards 00:01:38.150 --> 00:01:41.400 because there's a new package out 00:01:41.860 --> 00:01:42.940 that I want to talk about, 00:01:43.030 --> 00:01:46.800 but it's based on this article from Emma Levitt. 00:01:47.180 --> 00:01:51.020 Why in 2025 do we still need a third-party app 00:01:51.130 --> 00:01:53.560 to write a REST API with Django? 00:01:54.100 --> 00:02:01.220 So and third-party apps we're talking about is usually Django REST framework or Django Ninja. 00:02:02.080 --> 00:02:04.100 Increasingly more people are reaching for Django Ninja. 00:02:05.700 --> 00:02:07.140 But, you know, both are great choices. 00:02:07.780 --> 00:02:14.500 And but still, like, why do we have to have an extra REST framework with if you already have Django? 00:02:15.040 --> 00:02:22.020 And the basically the gist of this article is, no, you can you can create and with all the built ins. 00:02:22.220 --> 00:02:30.980 And this is using the class-based views to build a CRUD app, a CRUD API with Django. 00:02:31.160 --> 00:02:33.120 And I actually kind of love this. 00:02:33.900 --> 00:02:36.300 There's comments at the end also. 00:02:37.100 --> 00:02:42.580 I kind of love the article talking about doing everything that's necessary to, it's not that much, 00:02:42.680 --> 00:02:50.220 it's just not that much code to create a JSON REST API through, yeah, through Django without anything extra. 00:02:50.960 --> 00:02:58.220 And down in the comments, some of the folks are like, well, why would you do this if you already have these others? 00:02:58.700 --> 00:03:01.120 And of course, it's that you can. 00:03:03.300 --> 00:03:14.380 That you can, but also that when you understand how you could build it with just the tools here, then it helps you understand how to use the other tools like Django Ninja. 00:03:15.400 --> 00:03:22.580 So the reason why I'm bringing this up now, this is this, I think this article was from like March, April or something like that. 00:03:22.900 --> 00:03:29.140 But she went ahead and DJ Rest 2 is now available. 00:03:29.550 --> 00:03:38.000 And that is, if you scroll down to the bottom of it, it is her, is designed to be a minimal yet powerful Rest framework. 00:03:38.320 --> 00:03:43.640 but it's around this article of why do we need an external app for REST, 00:03:43.880 --> 00:03:47.560 which is kind of funny that she created an external app for REST too, 00:03:47.940 --> 00:03:49.040 to demonstrate that. 00:03:50.300 --> 00:03:52.340 But it's all the code from there. 00:03:52.540 --> 00:03:57.360 And it's really great to be able to learn about REST frameworks 00:03:57.700 --> 00:03:59.660 through trying something smaller scale. 00:04:00.120 --> 00:04:00.920 So I like it. 00:04:01.120 --> 00:04:01.420 Awesome. 00:04:01.900 --> 00:04:04.260 Yeah, I'm with her on this. 00:04:04.600 --> 00:04:06.140 You don't necessarily need a framework. 00:04:06.220 --> 00:04:07.100 I know there's great frameworks. 00:04:07.180 --> 00:04:11.260 like there's FastAPI and others and no shade on those things. 00:04:11.540 --> 00:04:15.980 But if you already have a web app, you already have a framework that is serving web stuff. 00:04:16.109 --> 00:04:19.260 And do you really want to say, well, now we're going to do a completely different one because 00:04:19.290 --> 00:04:21.079 I need the response to be JSON? 00:04:21.900 --> 00:04:22.900 Not necessarily, right? 00:04:23.000 --> 00:04:29.260 It's all the APIs that power the talk Python mobile app are written in pyramid. 00:04:29.760 --> 00:04:32.460 They're not using FastAPI because the whole app was already pyramid. 00:04:32.530 --> 00:04:35.960 The data, everything it needs to know about the users and the data and the course, it's 00:04:36.120 --> 00:04:36.560 all in there. 00:04:36.860 --> 00:04:42.100 And all I had to do is write a JSON serializer that would take a dictionary and turn into the right kind of JSON. 00:04:42.520 --> 00:04:43.540 And literally, I have an API. 00:04:43.780 --> 00:04:46.440 You know, a lot of these frameworks, I don't like them. 00:04:46.840 --> 00:04:48.200 I'm not knocking on any particular. 00:04:49.220 --> 00:04:55.500 But these add rest to your thing so often become what that means is an HTTP view of your database. 00:04:56.040 --> 00:05:01.440 Like, here's how you do get, post, put, and delete to rows in this table. 00:05:01.840 --> 00:05:04.700 And then, you know, it's like, okay, that's not the way I want to structure my. 00:05:05.220 --> 00:05:07.200 I don't want to just give my database to like the world. 00:05:07.290 --> 00:05:09.560 I want to have control over actions that you take, 00:05:09.690 --> 00:05:10.660 like authenticate. 00:05:10.830 --> 00:05:12.760 And that's not like just access to the table, 00:05:12.960 --> 00:05:13.460 you know, it's weird. 00:05:13.860 --> 00:05:14.520 So I don't know. 00:05:14.520 --> 00:05:16.040 I find them not to be, 00:05:16.070 --> 00:05:17.120 I know it's like, 00:05:17.200 --> 00:05:19.040 well, we absolutely have to reach for a rest thing. 00:05:19.150 --> 00:05:20.440 I don't know that that's necessarily true. 00:05:20.720 --> 00:05:24.260 It's also very true that you don't like, 00:05:24.500 --> 00:05:25.740 you don't really need a full framework 00:05:25.920 --> 00:05:27.160 if really you're the client. 00:05:28.120 --> 00:05:29.980 If, I mean, I would say, 00:05:30.300 --> 00:05:33.339 I would probably lean on others to create a better API 00:05:33.360 --> 00:05:37.280 or better experience if that's the product, 00:05:37.480 --> 00:05:38.740 if the API is the product. 00:05:38.860 --> 00:05:40.440 But if the product is your website 00:05:40.620 --> 00:05:43.400 and you've got a framework, you're using Django, 00:05:43.800 --> 00:05:45.240 you've got a database there, 00:05:45.500 --> 00:05:48.380 but you have something else that wants to access that data 00:05:49.200 --> 00:05:52.560 so that you're presenting some extra endpoints. 00:05:52.900 --> 00:05:54.540 If you just have a couple of endpoints 00:05:54.540 --> 00:05:57.840 that you need to create to get some data out 00:05:58.060 --> 00:06:00.040 or push some data in, 00:06:00.100 --> 00:06:03.660 you don't necessarily need the full-blown extra framework. 00:06:03.820 --> 00:06:05.740 I think something simple would work just fine. 00:06:05.960 --> 00:06:06.680 Yeah, for sure. 00:06:07.260 --> 00:06:07.420 Yeah. 00:06:08.460 --> 00:06:10.460 Well, let's get out of the web a little bit 00:06:10.580 --> 00:06:12.480 and maybe go to the command line. 00:06:13.340 --> 00:06:13.860 I'm going to spend a lot. 00:06:14.000 --> 00:06:17.280 I basically have a theme running through this, 00:06:17.840 --> 00:06:19.700 my picks, my topics for the day. 00:06:20.600 --> 00:06:23.220 So use git on the command line, I'm sure, Brian. 00:06:23.600 --> 00:06:23.660 Yeah. 00:06:23.660 --> 00:06:27.060 A little bit of git add, dot, git push, all those things. 00:06:27.220 --> 00:06:29.020 I'm a big fan of using the GUI tools, 00:06:29.240 --> 00:06:31.260 especially the tools built into your IDE, 00:06:31.620 --> 00:06:34.300 you know, PyCharm and VS Code plus derivatives. 00:06:34.480 --> 00:06:36.600 That means like 20 different things these days. 00:06:37.440 --> 00:06:39.180 They have really fantastic tools. 00:06:39.740 --> 00:06:41.860 And I don't rarely, I rarely feel the need, 00:06:41.940 --> 00:06:44.280 like I got to be in the command line to mess with it, 00:06:44.540 --> 00:06:45.400 but I still do plenty. 00:06:45.900 --> 00:06:48.660 That said, where I haven't been doing a lot of stuff 00:06:49.000 --> 00:06:51.740 in the command line is at the GitHub level. 00:06:52.360 --> 00:06:52.940 Oh, right, yeah. 00:06:53.300 --> 00:06:55.300 Right, like you're like, okay, I'm going to git push, get pull. 00:06:55.320 --> 00:06:57.520 Oh, there's a PR, I need to check that out. 00:06:57.660 --> 00:07:00.020 what is the command again to check out that PR? 00:07:01.560 --> 00:07:04.360 Or I want to refer to an issue. 00:07:04.750 --> 00:07:05.340 How do I do that? 00:07:05.480 --> 00:07:06.660 Like, what was the number of it again? 00:07:06.900 --> 00:07:08.600 Because there's really cool things in Git. 00:07:08.600 --> 00:07:09.400 You can say Git commit. 00:07:09.790 --> 00:07:11.300 And for the message, you can say, 00:07:12.820 --> 00:07:15.580 fixes or resolves number one, two, three. 00:07:15.750 --> 00:07:17.800 And that'll literally associate the commit 00:07:17.830 --> 00:07:19.600 with the issue one, two, three, and close it 00:07:19.750 --> 00:07:20.660 when you push it into the server. 00:07:20.910 --> 00:07:22.120 Which sometimes surprises me. 00:07:22.420 --> 00:07:23.520 But yeah, it's good to know. 00:07:23.640 --> 00:07:27.140 Yeah, I've accidentally put an issue in a PR, 00:07:27.220 --> 00:07:29.320 but then close the PR and it's closed issue. 00:07:29.370 --> 00:07:30.560 I'm like, no, no, no, that's actually, 00:07:31.610 --> 00:07:32.520 we're not done yet, hold on. 00:07:32.740 --> 00:07:35.140 Look, doesn't quite resolve blah. 00:07:36.060 --> 00:07:36.360 Whoops. 00:07:36.760 --> 00:07:38.520 Yeah, then it actually closes it. 00:07:38.520 --> 00:07:39.220 You got to reopen it. 00:07:39.360 --> 00:07:39.600 Whoopsie. 00:07:40.080 --> 00:07:42.700 Anyway, so what I want to talk about today 00:07:43.020 --> 00:07:45.780 is the GitHub CLI. 00:07:46.240 --> 00:07:47.840 So I don't know how long this has been around, 00:07:48.640 --> 00:07:50.960 well, presumably, but I think it's pretty new. 00:07:51.250 --> 00:07:55.160 And so the idea is you can ask for status of PRs 00:07:55.520 --> 00:07:56.740 or you can check out, 00:07:56.960 --> 00:07:57.640 Like this one's really nice. 00:07:59.219 --> 00:08:00.400 GHPR checkout 12. 00:08:00.800 --> 00:08:01.120 That's it. 00:08:01.320 --> 00:08:01.920 It's all you got to do. 00:08:02.340 --> 00:08:03.440 And it's figured out the branches. 00:08:03.840 --> 00:08:04.600 It's pulled it. 00:08:04.640 --> 00:08:06.160 It's checked out the right one, right? 00:08:06.320 --> 00:08:07.260 That's really cool, isn't it? 00:08:07.480 --> 00:08:07.880 Oh, yeah. 00:08:08.360 --> 00:08:08.440 Yeah. 00:08:08.600 --> 00:08:12.100 So to get a sense of what's possible, because when I saw this, I'm like, I think this will 00:08:12.100 --> 00:08:12.980 be cool, but why? 00:08:14.020 --> 00:08:14.480 Look at the manual. 00:08:14.660 --> 00:08:16.580 And the manual has example usages. 00:08:17.060 --> 00:08:18.780 That's how I would start to look. 00:08:18.940 --> 00:08:21.460 So it says, I could check out a pull request locally. 00:08:21.620 --> 00:08:22.760 And it's the one that I just said. 00:08:23.080 --> 00:08:23.220 Boom. 00:08:23.580 --> 00:08:23.700 Right. 00:08:24.040 --> 00:08:24.380 Pretty neat. 00:08:24.640 --> 00:08:25.720 You can do it by branch name. 00:08:26.260 --> 00:08:30.420 You can clone a repository with just the owner and repo. 00:08:30.680 --> 00:08:33.460 So you could say ghrepo clone, you know, 00:08:33.880 --> 00:08:37.479 Mike C. Kennedy slash Jinja dash partials or whatever. 00:08:37.680 --> 00:08:38.659 You don't have to know the whole URL. 00:08:38.800 --> 00:08:40.340 It's not that huge of a thing, but it's kind of nice. 00:08:40.640 --> 00:08:43.080 You can also clone it as if you were doing git clone, 00:08:43.200 --> 00:08:46.000 but you like to type gh-based repo instead of git. 00:08:46.320 --> 00:08:46.700 I don't know. 00:08:47.220 --> 00:08:51.440 You can create PRs from a branch, which is pretty cool. 00:08:51.740 --> 00:08:54.800 And it just asks you what's the title, what's the body, and so on. 00:08:55.360 --> 00:08:57.820 You can open up the browser, like take me to GitHub. 00:08:58.260 --> 00:08:59.340 You can mess with forks. 00:09:00.080 --> 00:09:00.820 What else can you do? 00:09:01.220 --> 00:09:03.540 Yeah, you can see issues like GitHub PR list. 00:09:04.160 --> 00:09:06.840 It'll show you whether they're open, who they're associated with. 00:09:07.120 --> 00:09:07.860 Same thing for issues. 00:09:08.340 --> 00:09:11.480 It even puts the tag in parentheses, parenthetically tags it. 00:09:11.480 --> 00:09:11.840 I love it. 00:09:12.060 --> 00:09:13.460 Anyway, I think this is kind of handy. 00:09:13.610 --> 00:09:13.980 What do you think? 00:09:14.300 --> 00:09:17.060 Yeah, you can do releases too, right? 00:09:17.430 --> 00:09:18.860 Did you already comment on that? 00:09:19.100 --> 00:09:20.040 I have not commented on that. 00:09:20.800 --> 00:09:23.120 Because that's often the thing that I need to, 00:09:23.350 --> 00:09:25.080 like I've got everything all automated. 00:09:25.140 --> 00:09:28.860 except for I still go over to GitHub itself 00:09:30.080 --> 00:09:32.180 to create a release item or release. 00:09:32.220 --> 00:09:33.300 Yeah, I do too. 00:09:33.660 --> 00:09:35.840 So being able to do that locally, that's pretty cool. 00:09:36.160 --> 00:09:38.820 I've got the generation of the release notes automated 00:09:39.120 --> 00:09:41.080 and the tagging of the branch automated, 00:09:41.210 --> 00:09:42.980 but I still can't release it automatically. 00:09:43.340 --> 00:09:43.640 You know what I mean? 00:09:43.920 --> 00:09:46.560 Now you can do it, at least do it on the command line. 00:09:46.680 --> 00:09:47.220 A little bit more. 00:09:47.520 --> 00:09:47.780 That's awesome. 00:09:48.380 --> 00:09:50.860 Anyway, check this out if you're a CLI person, 00:09:51.520 --> 00:09:53.220 you know, GH, your new command. 00:09:53.460 --> 00:09:54.720 Yeah, so go figure. 00:09:54.880 --> 00:09:56.760 that you're the command line person today 00:09:56.820 --> 00:09:58.060 and I'm the web person. 00:09:59.480 --> 00:10:01.780 So we're going to hop back over the web 00:10:02.040 --> 00:10:03.580 and talk about web scraping. 00:10:04.060 --> 00:10:07.540 So, and web scraping is, you know, not evil. 00:10:08.360 --> 00:10:11.120 Sometimes it's, especially if there's no API, 00:10:11.920 --> 00:10:13.980 it might be the only way to get some data from something. 00:10:15.200 --> 00:10:18.460 So there's a project that I found out on Reddit 00:10:19.540 --> 00:10:22.940 called Can I Scrape, which is sort of a fun name. 00:10:23.660 --> 00:10:35.860 And it basically analyzes the website's anti-bot protections to let you know whether or not you should even try to build a scraper for it or how many roadblocks you're going to run into. 00:10:36.960 --> 00:10:44.700 And also, I think it's just sort of, I don't know, it seems like kind of a nice thing to do instead of to check all the rules out and stuff. 00:10:44.780 --> 00:10:52.880 So it looks for protections like, I don't know what WAF is, but captures and rate limits, honeypots. 00:10:54.700 --> 00:11:06.680 And then it rates it a difficulty score from zero to 10, easy to hard, and specific recommendations on what tools or proxies you'll need and the estimated complexity to build it. 00:11:07.920 --> 00:11:13.720 that would be a decent thing to use on your own stuff if you are intending somebody, 00:11:13.970 --> 00:11:17.340 if you just tell somebody, oh, I don't have an API for that, but go scrape the data. 00:11:17.760 --> 00:11:20.620 What kind of a job are you asking them to do? 00:11:21.480 --> 00:11:25.400 And I was like, I didn't see right away a comment on the robots, 00:11:26.350 --> 00:11:31.920 but looking down through it, what it analyzes, it does check the robots.txt to make sure that you can. 00:11:32.090 --> 00:11:36.140 And that's one of the things I want to be careful of somebody's, 00:11:36.400 --> 00:11:38.680 what they say you should do and not do with their website. 00:11:39.860 --> 00:11:40.520 So that's cool. 00:11:40.940 --> 00:11:43.100 And anyway, I just thought it was nice. 00:11:43.520 --> 00:11:48.160 There's an interesting discussion on the link to the Reddit discretion as well. 00:11:49.120 --> 00:11:53.540 Just a target audience of hobbyists, but also just like data people. 00:11:53.770 --> 00:11:57.460 Like sometimes there's data that's available on the web that, like I said, 00:11:57.490 --> 00:12:00.540 no, there's no REST API yet for it or there won't be. 00:12:00.880 --> 00:12:01.660 But yeah, anyway. 00:12:01.940 --> 00:12:02.480 Yeah, I love it. 00:12:02.770 --> 00:12:03.240 Very interesting. 00:12:03.480 --> 00:12:09.380 This whole web scraping thing is getting more and more contentious with AI training and all of that. 00:12:09.580 --> 00:12:10.960 It's good to be a good citizen of the web. 00:12:11.320 --> 00:12:11.500 Yeah. 00:12:11.640 --> 00:12:15.760 And also, like, maybe I'd possibly use some of these to check your own. 00:12:15.800 --> 00:12:28.480 If you want to lock it down, if you really want to make, if you want to make scraping a real pain in the butt for people looking at your website, you know, you can use this to try to make your score as close to 10 as possible. 00:12:30.220 --> 00:12:30.620 Exactly. 00:12:31.060 --> 00:12:31.180 Exactly. 00:12:31.560 --> 00:12:31.800 All right. 00:12:32.360 --> 00:12:33.580 That's not what I want to talk about. 00:12:33.680 --> 00:12:35.140 That's what I want to talk about next. 00:12:36.060 --> 00:12:39.680 So I want to talk about Git, a totally different tool, though. 00:12:39.780 --> 00:12:41.120 This is completely unrelated to the other one. 00:12:41.790 --> 00:12:44.740 Okay, so I launched this CLI tool. 00:12:44.940 --> 00:12:51.900 It's on PyPI, but primarily is intended to be used as a CLI type of thing, 00:12:51.990 --> 00:12:55.000 like rough, not to be built upon, but to be run. 00:12:55.260 --> 00:12:55.560 You know what I mean? 00:12:55.690 --> 00:12:57.260 So you can uv tool install it. 00:12:57.640 --> 00:13:02.160 And the idea is I called it Giddyup, G-I-T-T-Y. 00:13:02.200 --> 00:13:07.060 for updating your, a whole directory tree of GitHub repositories. 00:13:07.550 --> 00:13:07.680 Okay. 00:13:08.060 --> 00:13:11.220 I may have talked about this before, something I kind of built like in passing. 00:13:11.720 --> 00:13:16.840 And then I was, last week I decided I'm creating a new course, 00:13:17.560 --> 00:13:19.100 Agentic AI programming in Python. 00:13:19.290 --> 00:13:19.740 How about that? 00:13:20.100 --> 00:13:23.940 And I'm like, let me think of something I can try to take that I know is a cool idea 00:13:23.990 --> 00:13:28.120 that would seem plausible, but really just make it a super nice app. 00:13:28.290 --> 00:13:30.120 Add a bunch of features and so on. 00:13:30.500 --> 00:13:35.680 So I took that little utility I had and I spent a lot of time with CloudSonna and Giddyup 00:13:35.860 --> 00:13:36.860 is the output. 00:13:37.960 --> 00:13:40.120 So it says, never forget to pull again. 00:13:40.380 --> 00:13:42.920 Automatically discover and update all your GitHub repositories in one command. 00:13:43.120 --> 00:13:44.160 So here's the thing. 00:13:44.260 --> 00:13:48.380 I've got three computers, one of them is a laptop, and they all have a bunch of GitHub 00:13:48.640 --> 00:13:50.900 repositories, like hundreds of GitHub repositories. 00:13:51.400 --> 00:13:52.200 And it drives me crazy. 00:13:52.360 --> 00:13:54.840 I'll go to some older one I haven't worked with for a while. 00:13:55.140 --> 00:13:56.560 Like, I don't think there's been any change to this. 00:13:56.570 --> 00:13:57.460 And I'll start messing with it. 00:13:57.560 --> 00:13:58.580 Then I'll try to push it. 00:13:58.580 --> 00:14:00.080 It'll go, please pull your changes first. 00:14:00.280 --> 00:14:02.440 I'm like, uh-oh, uh-oh, that's not good, 00:14:03.160 --> 00:14:04.780 especially if it's something to do with the courses 00:14:05.060 --> 00:14:07.880 where it might be a PowerPoint that cannot be merged. 00:14:08.260 --> 00:14:08.680 You know what I mean? 00:14:08.840 --> 00:14:10.520 You're like, oh, no, this is real bad. 00:14:11.360 --> 00:14:12.380 And it's out of date, right? 00:14:12.900 --> 00:14:14.420 And so I created this thing so I can just, 00:14:14.660 --> 00:14:17.420 especially before I grab my laptop and head off to the coffee shop, 00:14:17.520 --> 00:14:20.840 I can just go into part of my GitHub repos and just say, Giddyup. 00:14:21.040 --> 00:14:22.300 And it goes through in parallel, 00:14:22.840 --> 00:14:24.660 and it just looks at all the repositories. 00:14:25.140 --> 00:14:27.820 Does it get pull on all the ones that don't have anything checked out? 00:14:27.860 --> 00:14:29.500 And the ones that are not committed yet, 00:14:29.660 --> 00:14:30.900 It says, hey, I don't want to mess with this one. 00:14:30.990 --> 00:14:33.360 It has these three files unchanged and so on. 00:14:33.530 --> 00:14:37.560 So it's just like a nice little utility people can run to update all their code. 00:14:37.590 --> 00:14:39.460 I'll see if I can find a little output down here. 00:14:39.980 --> 00:14:40.900 It's got a ton of features. 00:14:41.010 --> 00:14:43.480 But yeah, I'd say update this thing, 00:14:43.530 --> 00:14:47.560 and it traverses hierarchically through all the GitHub repositories. 00:14:47.610 --> 00:14:48.580 It says these are up to date. 00:14:48.760 --> 00:14:50.620 I actually pulled a couple commits for this one. 00:14:50.900 --> 00:14:52.400 This one had an error, and it just gives you, 00:14:52.800 --> 00:14:56.339 basically gets all of your GitHub repositories as much in sync 00:14:56.560 --> 00:14:58.560 across all the branches as much as possible 00:14:58.860 --> 00:14:59.560 without breaking anything. 00:14:59.840 --> 00:15:00.160 Oh, cool. 00:15:00.440 --> 00:15:02.260 Yeah, so anyway, I put that out there for you. 00:15:02.260 --> 00:15:04.000 I think people might like it. 00:15:04.120 --> 00:15:06.860 I didn't, I just put it out there two days or three days ago 00:15:07.120 --> 00:15:09.580 and it's already got some stars and forks 00:15:09.580 --> 00:15:11.340 and I haven't announced it at all whatsoever, 00:15:11.720 --> 00:15:12.560 not even on social media. 00:15:12.980 --> 00:15:14.760 So people found it and started, that's cool. 00:15:15.060 --> 00:15:15.640 Yeah, nice. 00:15:16.140 --> 00:15:17.160 All right, so GittyUp. 00:15:18.000 --> 00:15:21.400 I have a feeling that maybe people watch your repo 00:15:21.640 --> 00:15:22.160 a little bit. 00:15:22.480 --> 00:15:24.360 I think that's what it is, like the GitHub. 00:15:24.820 --> 00:15:32.160 And to be honest, I am a super fan of just clicking on the GitHub logo and going and just looking at what's flowing by. 00:15:32.400 --> 00:15:33.980 I'm starting to follow more and more people. 00:15:34.170 --> 00:15:35.300 I appreciate people following me. 00:15:35.960 --> 00:15:38.800 That's a really nice source of just, hey, what's interesting? 00:15:39.220 --> 00:15:42.200 Because if people you follow star something, that shows up. 00:15:42.300 --> 00:15:45.720 You're like, oh, this person found that interesting enough to star it. 00:15:46.010 --> 00:15:47.960 And I definitely respect what that person is doing. 00:15:48.360 --> 00:15:49.160 Let me go check this out. 00:15:49.210 --> 00:15:50.120 That does look interesting. 00:15:50.820 --> 00:15:52.080 I'm sure that's how people found it. 00:15:52.300 --> 00:15:53.020 Okay, cool. 00:15:53.080 --> 00:15:53.540 Yeah, cool. 00:15:54.420 --> 00:16:00.040 Well, I want to bring up something that I've apparently spent a lot of time thinking about. 00:16:00.690 --> 00:16:02.840 So we're done with our normal stuff, right? 00:16:03.140 --> 00:16:03.640 We are. 00:16:04.100 --> 00:16:05.340 Moving on to extras. 00:16:06.110 --> 00:16:07.320 Do you want to do your extras first? 00:16:08.160 --> 00:16:08.400 Sure. 00:16:08.650 --> 00:16:09.720 I'll be quick about mine. 00:16:09.790 --> 00:16:09.880 Okay. 00:16:10.520 --> 00:16:11.140 Yeah, let's do yours. 00:16:11.750 --> 00:16:12.700 Let me close this off. 00:16:12.770 --> 00:16:14.620 Yeah, check out that Agentic AI programming course. 00:16:14.760 --> 00:16:15.600 It's coming out this week. 00:16:16.640 --> 00:16:17.880 But people listened. 00:16:18.240 --> 00:16:19.260 And I don't know if they actually listened to us. 00:16:19.260 --> 00:16:21.280 I think they listened to other people with the same complaint. 00:16:21.560 --> 00:16:28.480 But remember how last week on PyDay, I said, great, but uv loop doesn't work with Python 3.14. 00:16:28.960 --> 00:16:32.860 Well, I'm so happy to tell you as of four days ago, uv loop is back, baby. 00:16:33.400 --> 00:16:38.740 And we can use it again, which mostly is awesome because I don't want to go change a bunch of projects that were just fine. 00:16:39.140 --> 00:16:44.000 But if I were to swap out the foundation running them like to 3.14, they wouldn't run anymore. 00:16:44.150 --> 00:16:44.980 So now it's back. 00:16:44.980 --> 00:16:46.800 So there's a release for that. 00:16:47.180 --> 00:16:51.360 So uv loop, while it was gone from us for a little bit, it's back. 00:16:51.840 --> 00:16:56.380 And remember how I said, I wish I knew who created PyPI plus and how neat it was, because 00:16:56.440 --> 00:16:59.680 it has just these few little gotchas that I would love to like polish it. 00:17:00.100 --> 00:17:04.459 Well, they sent over a message and said, thank you so much for a feature in PyPI plus, and 00:17:04.500 --> 00:17:05.699 I'm working on the bugs that you found. 00:17:06.589 --> 00:17:09.900 I don't know how they heard that we were maybe their show listener or someone they know is 00:17:09.900 --> 00:17:10.699 a listener of the show. 00:17:11.020 --> 00:17:11.579 But yeah, look at this. 00:17:11.699 --> 00:17:15.079 I can search for something with a dash and I get the lowercase and vice versa. 00:17:15.480 --> 00:17:15.780 Oh, cool. 00:17:16.839 --> 00:17:23.280 But also, there's some people that maybe don't have a Python podcast to complain about things. 00:17:24.740 --> 00:17:28.760 Is there like a about us or who are we? 00:17:28.880 --> 00:17:29.320 There is. 00:17:29.320 --> 00:17:34.360 I believe I put it in, you know, the best way would be a Reddit, I believe. 00:17:34.540 --> 00:17:40.140 So Royal Wizard is the one who they initially announced it on Reddit and so on. 00:17:40.140 --> 00:17:45.279 So you could, and they seem to be talking about the changes and the features over on 00:17:45.320 --> 00:17:51.680 slash r you know r slash python so that's probably the best way okay yeah cool and then finally i you 00:17:51.680 --> 00:17:57.660 know i told you about my host show me your ls which looked like show me your is because of the fonts 00:17:58.030 --> 00:18:03.000 well people uh sent some feedback and i just wanted to share one because this is a common theme over 00:18:03.120 --> 00:18:08.920 and over thomas spenson uh said hey i'm currently using new shell which for some reason i read as a 00:18:08.920 --> 00:18:12.839 nutshell and went about talking about it that stuff that was the thing but said hey i'm currently using 00:18:13.080 --> 00:18:17.160 and exploring New Shell, and its LS is something else clever. 00:18:18.780 --> 00:18:23.800 So you can just kind of do almost query syntax against things like LS, 00:18:24.200 --> 00:18:26.680 structured data, PS, JSON, et cetera. 00:18:27.060 --> 00:18:27.740 So like, look at this. 00:18:28.040 --> 00:18:28.860 This is crazy, right? 00:18:29.220 --> 00:18:29.460 Yeah. 00:18:29.740 --> 00:18:33.540 And following on, found out today that New Shell is using Polars 00:18:33.540 --> 00:18:35.800 and that plugins can be written in Python. 00:18:36.420 --> 00:18:37.340 So even cooler. 00:18:37.740 --> 00:18:39.040 I'm not doing anything with New Shell. 00:18:39.350 --> 00:18:40.680