WEBVTT 00:00:00.040 --> 00:00:04.660 Hello and welcome to Python Bytes, where we deliver Python news and headlines directly to your earbuds. 00:00:05.130 --> 00:00:10.240 This is episode 467, recorded January 26, 2026. 00:00:10.570 --> 00:00:11.880 Ooh, that's a lot of 26s. 00:00:12.200 --> 00:00:13.200 I'm Brian Okken. 00:00:13.460 --> 00:00:14.220 I'm Michael Kennedy. 00:00:14.560 --> 00:00:22.420 This episode is sponsored by all of us, all of you, and the products that we have going at Python Bytes, 00:00:22.720 --> 00:00:28.520 and I guess not at Python Bytes, but Talk Python Training, and at pythontest.com, 00:00:28.580 --> 00:00:34.060 We've got the pytest course and LeanTDD, but Michael's got courses and books and all sorts of fun stuff. 00:00:34.500 --> 00:00:36.020 And also, of course, Patreon supporters. 00:00:36.320 --> 00:00:37.940 We still love you. 00:00:38.500 --> 00:00:44.080 And yeah, if you'd like to connect with us and send us topics, maybe topics for the show, we love that. 00:00:44.440 --> 00:00:50.640 You can just send us through the contact form at pythonbytes.fm, but you can also find us on the socials. 00:00:51.580 --> 00:00:52.920 And the links are in the show notes. 00:00:53.060 --> 00:00:54.840 We're on Bluesky and Mastodon. 00:00:55.620 --> 00:00:59.320 Yeah, and if you'd like to see what we look like 00:00:59.880 --> 00:01:02.420 or watch us live or tape recorded, 00:01:03.100 --> 00:01:05.820 you can go to pythonbytes.fm/live 00:01:06.120 --> 00:01:07.780 and yeah, check out that. 00:01:08.040 --> 00:01:10.020 And it tells you when we're going to show next time. 00:01:10.180 --> 00:01:11.900 Yeah, they can even check out a glimpse 00:01:12.200 --> 00:01:15.540 of the Python staff of power just behind you there. 00:01:15.620 --> 00:01:16.300 Yeah, that's right. 00:01:17.000 --> 00:01:17.680 Yeah, there it is. 00:01:19.220 --> 00:01:21.400 Yeah, and I'm still on the fence 00:01:21.540 --> 00:01:23.000 about going to PyCon this year. 00:01:23.070 --> 00:01:24.060 And if I go to PyCon, 00:01:24.300 --> 00:01:25.920 I'll definitely bring the staff of power. 00:01:26.560 --> 00:01:29.440 My fence has been built and decided upon. 00:01:29.590 --> 00:01:33.360 I bought my tickets and I got actually a pretty amazing deal on Expedia. 00:01:34.140 --> 00:01:42.980 I was able to get four days hotel right near a block or two from the convention center and the water and a round trip flight for 600 bucks total. 00:01:43.340 --> 00:01:43.740 So I'm going. 00:01:44.080 --> 00:01:44.900 Oh, nice. 00:01:45.440 --> 00:01:45.540 Yeah. 00:01:45.920 --> 00:01:51.520 I'm going to try to ask work if I can get away with not having to take vacation time to go. 00:01:52.240 --> 00:01:52.900 Yeah, wouldn't that be nice? 00:01:53.160 --> 00:01:54.460 Hey, they talk about pytest there. 00:01:54.510 --> 00:01:55.540 I know you're doing a lot with that. 00:01:55.860 --> 00:01:56.020 Yeah. 00:01:56.290 --> 00:01:56.980 So, all right. 00:01:57.090 --> 00:01:59.420 Well, should we do some topics for the show? 00:01:59.980 --> 00:02:00.640 Let's talk. 00:02:00.980 --> 00:02:02.200 Oh, I have the toad up. 00:02:02.360 --> 00:02:03.420 That is not what I want to talk about. 00:02:03.460 --> 00:02:06.720 I want to talk about this thing called the Gray Noise IP Check. 00:02:06.870 --> 00:02:07.000 Okay. 00:02:07.310 --> 00:02:14.040 So Gray Noise is a company that does research on cyber security breaches, 00:02:14.490 --> 00:02:15.340 et cetera, et cetera, right? 00:02:15.640 --> 00:02:15.740 Yeah. 00:02:16.060 --> 00:02:20.000 So they have published this thing called the Gray Noise IP Check. 00:02:20.560 --> 00:02:26.480 And if you just go to check.labs.greynoise.io or way simpler, click the link in the show notes. 00:02:26.940 --> 00:02:30.900 It will take you to this place that says your IP address is whatever your IP address is. 00:02:31.360 --> 00:02:33.600 And your IP address is clean. 00:02:33.920 --> 00:02:41.560 Your IP has not been observed scanning the internet or contained in the common business services data set. 00:02:41.880 --> 00:02:42.840 So what is this for? 00:02:43.220 --> 00:02:51.360 Like in the day of 30 things connected to your internet, your Wi-Fi, with your kids installing random junk off the internet. 00:02:51.600 --> 00:02:52.760 Like my kid is pretty good. 00:02:52.860 --> 00:02:54.920 She says, dad, is it okay if I install this? 00:02:55.480 --> 00:02:56.440 Yes, it's okay or no. 00:02:56.600 --> 00:03:02.540 And she actually completely reformatted her Windows 11 machine so she could play games but not worry about what was installed on it. 00:03:02.920 --> 00:03:04.680 So, you know, not knocking the kid or anything. 00:03:04.980 --> 00:03:06.380 But kids install stuff. 00:03:06.800 --> 00:03:08.040 Other people install stuff. 00:03:08.240 --> 00:03:14.320 Your TV, your smart power thing that goes to that lamp in the corner. 00:03:14.590 --> 00:03:17.540 You know, there's a crap ton of stuff that is on your network. 00:03:18.040 --> 00:03:20.340 And even if you run some sort of virus check on your computer, 00:03:21.080 --> 00:03:23.600 having that come up empty doesn't mean that there's not a problem 00:03:24.010 --> 00:03:25.720 with things that you are in control of, right? 00:03:26.120 --> 00:03:29.000 So basically the idea of this thing is you can go here 00:03:29.140 --> 00:03:32.700 and it will tell you if something on your network has been being bad. 00:03:32.960 --> 00:03:33.200 Okay. 00:03:33.660 --> 00:03:33.760 Yeah. 00:03:34.140 --> 00:03:36.220 And I don't know, for me, I thought that was pretty cool. 00:03:36.480 --> 00:03:41.940 So I threw it in as one of the topics so that other people can click on this and see, I guess, a couple caveats. 00:03:42.420 --> 00:03:48.720 If your IP address just changed recently, it's very plausible that you could get a warning. 00:03:49.140 --> 00:03:50.320 And it was whoever had it before. 00:03:50.800 --> 00:03:51.100 You know what I mean? 00:03:51.400 --> 00:03:54.620 Like we had a power outage for just a couple hours. 00:03:55.180 --> 00:03:59.680 Some sort of, I think I talked about this last time because my mic had gotten all reset. 00:03:59.900 --> 00:04:04.060 Because everything got powered 100% down because some sort of transformer thing exploded. 00:04:04.440 --> 00:04:05.980 We got a new IP address from then. 00:04:06.400 --> 00:04:08.180 Right. But, you know, a couple of weeks ago. 00:04:08.520 --> 00:04:11.200 And so it turns out that I guess things are still good. 00:04:11.360 --> 00:04:11.980 That's good to know. 00:04:12.700 --> 00:04:15.300 But if you just had your IP address change, 00:04:15.620 --> 00:04:18.060 then it could be picking up issues from whoever had it before. 00:04:18.590 --> 00:04:21.060 Right. Kind of like you keep getting spam with that new phone number you got. 00:04:21.859 --> 00:04:23.400 Yeah. But these, I don't know about you, 00:04:23.500 --> 00:04:26.520 but my IP address is pretty much rock solid stable. 00:04:26.810 --> 00:04:29.300 Unless something goes wrong with the internet or with power, 00:04:29.590 --> 00:04:30.240 then it may change. 00:04:30.420 --> 00:04:32.680 But other than that, it's the same for quite a while. 00:04:33.160 --> 00:04:37.840 I'm slightly embarrassed to say I usually don't know my IP address. 00:04:38.320 --> 00:04:42.460 And I actually don't quite get how, I mean, I get how IP addresses work. 00:04:42.680 --> 00:04:46.800 But like for a house, is your whole house like the same IP address? 00:04:47.300 --> 00:04:49.280 Or I don't know how that works. 00:04:51.000 --> 00:04:52.820 Also, like, does this, can you use this? 00:04:52.960 --> 00:04:56.980 Like if you're at a cafe to check to see if there's other like bad actors there? 00:04:57.100 --> 00:04:58.400 Yeah, I guess you probably could actually. 00:04:58.540 --> 00:04:58.640 Yeah. 00:04:58.960 --> 00:04:59.500 So, yeah. 00:04:59.840 --> 00:04:59.920 Anyway. 00:05:00.660 --> 00:05:01.000 Interesting. 00:05:01.380 --> 00:05:01.500 Okay. 00:05:01.880 --> 00:05:02.700 Well, I'll have to check it out. 00:05:02.760 --> 00:05:09.000 And I know more because I have a lot of my stuff gated behind IP addresses, like the server. 00:05:09.540 --> 00:05:14.320 You can't even SSH to the server unless your IP address is on a whitelist, right? 00:05:14.580 --> 00:05:17.520 So periodically when it changes, I'm like, oh, what is my IP address again? 00:05:17.670 --> 00:05:18.840 So then I go copy. 00:05:18.950 --> 00:05:23.620 I don't really pay too much attention, but because of that, I kind of got to pay a little attention. 00:05:23.940 --> 00:05:27.660 Yeah, I'm like a very data in the cloud sort of person. 00:05:28.060 --> 00:05:28.720 So I guess. 00:05:28.840 --> 00:05:28.960 Perfect. 00:05:29.240 --> 00:05:29.400 All right. 00:05:29.740 --> 00:05:34.900 Well, I'm very excited about this next topic that you have because I also saw it and said, that is killer. 00:05:35.440 --> 00:05:36.400 It is killer. 00:05:36.840 --> 00:05:36.960 Yeah. 00:05:37.220 --> 00:05:39.720 So what we're talking about is TPROF. 00:05:39.900 --> 00:05:41.460 This is from, or TPROF? 00:05:41.600 --> 00:05:42.420 I think it's TPROF. 00:05:42.660 --> 00:05:44.780 It's the targeting profiler from Adam Johnson. 00:05:45.560 --> 00:05:49.780 And we've got a link to the PyPA site. 00:05:50.760 --> 00:05:54.400 But it just mostly says, yeah, it's a targeting profiler. 00:05:54.640 --> 00:05:58.920 But we're also going to link to his article introducing it. 00:05:59.100 --> 00:06:06.820 introducing tprof a targeting profile profiler so that yeah so it's it almost speaks for itself 00:06:07.360 --> 00:06:13.700 what the what he's talking about is if you run a profiler on your program it gives you everything 00:06:13.950 --> 00:06:20.020 it like it and that and you do you want to do that at first to to see all the hot spots where 00:06:20.030 --> 00:06:24.940 are you spending your time and that's what you use profilers for to see where you know where you 00:06:24.960 --> 00:06:31.920 maybe could could optimize some of your some of your code and so but and once you pinpointed what 00:06:31.940 --> 00:06:37.300 you want to try to fix then you want to try to measure that and you kind of have to do and his 00:06:37.380 --> 00:06:42.580 his pain point was running running it over the whole program again and again and again and you 00:06:42.580 --> 00:06:47.540 don't really need to so his is a targeting profiler and you give it exactly the function that you're 00:06:47.600 --> 00:06:53.599 caring about or the functions multiple and it'll report what the times are like the minute max and 00:06:53.620 --> 00:06:58.620 stuff. And then he went further and said, there's a lot of times where you're just going to want to 00:06:58.640 --> 00:07:04.340 do like a before and after function. And it probably won't be before and after, but you can 00:07:04.440 --> 00:07:12.500 like my search routine old and my search routine new or something like that. And you can have those 00:07:12.660 --> 00:07:18.800 be targeted and run the results and compare those. Nice. It's like a showdown, right? Instead of 00:07:18.900 --> 00:07:23.200 trying to remember the results, you just say, here's the old way, here's the new way. How'd that 00:07:23.080 --> 00:07:28.080 turn out right. And he's kind of got two ways to do it. You can do like a, well, so you can do the 00:07:28.320 --> 00:07:33.660 past the functions that you want to want to look at on the command line. So you don't even 00:07:33.840 --> 00:07:39.820 have to actually change anything in your code to do this. You can just, you can just target a couple 00:07:39.900 --> 00:07:48.180 functions and, and call those. And then, but you can also do a dash X for a compare and it'll do 00:07:48.200 --> 00:07:50.820 a delta time, like a percent faster or a percent slower, 00:07:51.290 --> 00:07:51.920 which is pretty cool. 00:07:52.920 --> 00:07:56.280 Or you can not have to do the command line thing too much 00:07:56.330 --> 00:07:59.560 and just do as a context manager. 00:07:59.730 --> 00:08:02.460 You can say which ones you're going to compare 00:08:03.150 --> 00:08:05.500 and run those before and after with tprof. 00:08:06.480 --> 00:08:09.140 All those are, I probably use all of those 00:08:09.380 --> 00:08:12.600 at different times, but I'm really excited to try this 00:08:12.670 --> 00:08:15.700 to use, to optimize some code that I've been working on. 00:08:15.940 --> 00:08:16.960 So it's pretty neat. 00:08:17.340 --> 00:08:22.320 Apparently uses the new Python 3.12 profiling API, which is really nice. 00:08:22.610 --> 00:08:26.160 So a little using the modern lower touch profiler as well. 00:08:26.600 --> 00:08:26.720 Yeah. 00:08:26.770 --> 00:08:31.340 So of course, you have to run it with 3.12 or above, 00:08:31.760 --> 00:08:35.500 but that doesn't mean that the code that you're testing against 00:08:36.200 --> 00:08:38.000 is necessarily just 3.12 and above. 00:08:38.219 --> 00:08:40.260 It's just when you're running it, it'll be 3.12. 00:08:41.190 --> 00:08:43.060 You know what? 3.12 is almost obsolete. 00:08:43.370 --> 00:08:43.740 I'm serious. 00:08:44.090 --> 00:08:45.080 Like how insane is that? 00:08:45.380 --> 00:08:45.700 What? 00:08:46.580 --> 00:08:49.720 I mean, 3.10 is the oldest that is even allowed. 00:08:50.100 --> 00:08:53.840 Like 3.9 has gone into, like, we don't even do security patches anymore. 00:08:54.280 --> 00:08:55.980 Yeah, yeah, that's true. 00:08:56.230 --> 00:08:59.660 3.10 is on the shadow, and then, like, it's a few years until all that thing's gone. 00:08:59.920 --> 00:09:00.700 So it's not that old. 00:09:01.020 --> 00:09:04.700 And we don't even mention 2.7 anymore, the legacy. 00:09:05.420 --> 00:09:05.920 So good. 00:09:06.480 --> 00:09:08.960 So good to be past those days, right? 00:09:09.040 --> 00:09:38.140 I would also like to point out that this is just so good for profiling any real application, like any real application, because so much of what happens if you just see profile my particular app is all the time spent loading modules, all the time connecting to the database and just all of that, you know, setting up the log in that all, like all the stuff that happens before you get to the one function, you want to see what's going on. 00:09:38.260 --> 00:09:39.240 and then it stops and you're like, 00:09:39.540 --> 00:09:41.200 the thing only takes 50 milliseconds, 00:09:41.780 --> 00:09:43.760 but I've got profiling for like two seconds. 00:09:44.740 --> 00:09:46.060 And what is going on? 00:09:46.160 --> 00:09:48.100 It's just so lost in the noise. 00:09:48.620 --> 00:09:50.860 And then this one, you can just say, run it, 00:09:51.100 --> 00:09:52.860 let all that, just ignore all that junk. 00:09:53.200 --> 00:09:54.400 When you get to this function, start, 00:09:54.600 --> 00:09:55.760 when you're done with the function, stop. 00:09:56.140 --> 00:09:56.560 You know what I mean? 00:09:56.940 --> 00:09:58.400 Yeah, and that's actually, oh, 00:09:58.720 --> 00:10:00.660 that part of it's overwhelming to me. 00:10:00.880 --> 00:10:02.640 Every time I've had to reach, I don't have to, 00:10:02.820 --> 00:10:04.780 you know, it's like a lot of debugging tools. 00:10:04.860 --> 00:10:06.560 You don't have to reach for them all the time. 00:10:06.980 --> 00:10:11.100 But when you do, it's a little overwhelming to look at all that profiling output. 00:10:12.200 --> 00:10:15.360 And I still haven't got my head around flame graphs. 00:10:15.780 --> 00:10:16.340 But, you know. 00:10:16.560 --> 00:10:16.680 Yeah. 00:10:17.060 --> 00:10:17.360 Catch them. 00:10:17.580 --> 00:10:17.940 They're hot. 00:10:18.260 --> 00:10:26.920 No, honestly, like the fact you just say, just profile this function, and that actually happens on the CLI, my profiling is back, baby. 00:10:27.380 --> 00:10:32.200 Like, it's just, I'm like, is it really worth trying to dig through all that overhead and junk and decide, like, probably no. 00:10:32.570 --> 00:10:34.160 But now maybe it really is. 00:10:34.640 --> 00:10:35.020 Thanks, Adam. 00:10:35.760 --> 00:10:36.400 Yeah, thank you, Adam. 00:10:36.520 --> 00:10:41.440 And then one more thing is like a lot of times some things are slower the very, very first 00:10:41.640 --> 00:10:42.140 times they run. 00:10:42.660 --> 00:10:48.060 So it might be worth writing a function that actually like runs it a bunch of times or 00:10:48.560 --> 00:10:51.420 runs it once before you get to it and then profile. 00:10:51.840 --> 00:10:52.220 You know what I mean? 00:10:52.320 --> 00:10:56.700 Like just like, because it might be the module loading that actually overwhelms the compute, 00:10:56.960 --> 00:10:59.640 but that only happens once or, you know, do I see compilation? 00:11:00.160 --> 00:11:02.160 The context manager one would be great for that. 00:11:02.260 --> 00:11:04.560 then you could just, you could call both, 00:11:04.720 --> 00:11:06.500 like both the new and the old function once. 00:11:06.980 --> 00:11:07.240 Exactly. 00:11:07.860 --> 00:11:11.320 And then do a loop and do like a hundred times 00:11:11.560 --> 00:11:12.980 to the other two. 00:11:13.210 --> 00:11:14.660 Yeah, that would be totally perfect. 00:11:14.810 --> 00:11:15.780 That would be really, really good. 00:11:16.000 --> 00:11:17.720 You know what we don't talk enough about though, Brian? 00:11:18.040 --> 00:11:19.660 Honestly, I mean, toads. 00:11:20.040 --> 00:11:20.580 Let's talk about toads. 00:11:21.000 --> 00:11:22.740 I know, and we live in Oregon. 00:11:22.850 --> 00:11:23.900 We got them all over the place. 00:11:24.280 --> 00:11:24.780 We do. 00:11:25.090 --> 00:11:26.300 We do got them all over the place. 00:11:26.690 --> 00:11:27.320 Or frogs at least. 00:11:27.390 --> 00:11:28.580 I don't know if we have toads. 00:11:28.760 --> 00:11:29.720 I don't, you know what. 00:11:30.080 --> 00:11:32.720 So with Toad, this comes from Will McGuggan. 00:11:33.420 --> 00:11:35.820 It's kind of his next big thing that he's been working on 00:11:36.320 --> 00:11:37.600 since Textual. 00:11:38.280 --> 00:11:43.240 And the idea is it's kind of like a UI for Claude Code type 00:11:43.420 --> 00:11:43.500 things. 00:11:43.540 --> 00:11:45.660 It actually works with something called OpenHands. 00:11:45.860 --> 00:11:46.820 It works with Claude Code. 00:11:47.040 --> 00:11:49.780 It works with Gemini CLI, probably others 00:11:50.080 --> 00:11:50.700 that I don't know about. 00:11:51.000 --> 00:11:52.500 When I first saw this, I'm like, OK, well, 00:11:52.520 --> 00:11:53.380 I already have a terminal. 00:11:53.800 --> 00:11:54.300 I can do this. 00:11:54.300 --> 00:11:57.860 Like, what-- I'm not really entirely sure what I need this 00:11:58.000 --> 00:11:58.180 for. 00:11:58.540 --> 00:12:01.020 But the more I looked into it, it looks really quite neat. 00:12:01.440 --> 00:12:04.560 So if you go through, it obviously renders pictures. 00:12:05.120 --> 00:12:06.200 Apparently not there. 00:12:06.200 --> 00:12:06.880 It renders pictures. 00:12:07.520 --> 00:12:10.340 Like one of the pictures is the Mandelbrot set drawn. 00:12:10.740 --> 00:12:11.000 Cool. 00:12:11.240 --> 00:12:16.000 And it has really nice, basically better input. 00:12:16.840 --> 00:12:19.340 One of the challenges with things like Claude Code and friends 00:12:19.380 --> 00:12:20.500 is you're just in the terminal. 00:12:20.660 --> 00:12:24.360 And so can you use the mouse to select part of your text 00:12:24.480 --> 00:12:25.000 and cut it? 00:12:25.960 --> 00:12:27.360 No, it's the terminal, right? 00:12:28.500 --> 00:12:30.620 And the arrow keys work right and all those kinds of things. 00:12:31.070 --> 00:12:35.980 So it has a really nice, I'll just put this little video in the background while it's 00:12:36.100 --> 00:12:36.460 going here. 00:12:36.740 --> 00:12:39.420 I can get it to play and it doesn't want to play. 00:12:39.680 --> 00:12:45.640 Well, it has a really nice input for that kind of behavior, right? 00:12:45.880 --> 00:12:49.020 Has a nice little web server that runs. 00:12:49.900 --> 00:12:51.140 Let's see, a few more. 00:12:51.500 --> 00:12:53.000 It uses fuzzy search. 00:12:53.240 --> 00:12:56.160 So something you do all the time or should do all the time. 00:12:56.260 --> 00:12:57.940 And if you're not, you're totally missing out. 00:12:58.540 --> 00:13:03.540 adding files a specific context to what you're working on. 00:13:03.560 --> 00:13:07.520 So you might say, hey, I'd like to work on the login page. 00:13:07.920 --> 00:13:10.460 And here are the notes that I, you know, use the notes that I took. 00:13:10.900 --> 00:13:12.060 How well is it going to work? 00:13:12.160 --> 00:13:12.600 We don't know. 00:13:12.640 --> 00:13:16.580 You could say, I'd like to work on at login.html. 00:13:16.960 --> 00:13:22.280 And please see at login requirements.md, right? 00:13:22.440 --> 00:13:25.420 And that will actually pop up a select. 00:13:26.040 --> 00:13:30.800 And so this uses really nice fuzzy search and UI dropdowns in the terminal. 00:13:31.240 --> 00:13:32.380 It says better prompt input. 00:13:33.000 --> 00:13:37.020 It has support for terminals within terminals. 00:13:37.220 --> 00:13:41.260 So if you ask it to run a command that is like complex terminal output, 00:13:41.700 --> 00:13:43.600 it will actually embed that, which is really sweet. 00:13:43.920 --> 00:13:45.480 So people should give this a look. 00:13:45.740 --> 00:13:46.940 I think it's pretty nice. 00:13:47.500 --> 00:13:49.120 You know, pip install, I believe. 00:13:49.560 --> 00:13:50.420 I'm going to check it out. 00:13:50.720 --> 00:13:51.200 No, curl. 00:13:51.660 --> 00:13:52.440 Curl install it. 00:13:52.760 --> 00:13:53.020 Get it. 00:13:53.240 --> 00:13:54.080 That's the new way, right? 00:13:54.360 --> 00:13:55.380 UV is showing us the way. 00:13:55.500 --> 00:13:57.640 But you can also uv tool install it if you prefer. 00:13:58.140 --> 00:14:05.600 And that's probably the way I would install it because I already have scripts that basically manage all of my uv tools, check for updates and so on. 00:14:05.920 --> 00:14:11.100 So check out Toad if you're doing like CLI cloud code like things. 00:14:11.560 --> 00:14:12.260 Yeah, cool. 00:14:12.960 --> 00:14:13.060 Yeah. 00:14:14.480 --> 00:14:14.960 Batrachain. 00:14:15.460 --> 00:14:15.940 Batrachain. 00:14:16.120 --> 00:14:16.740 I don't know. 00:14:16.820 --> 00:14:22.760 The girl is pulling it from a URL called B-A-T-R-A-C-H-I-A-N. 00:14:23.300 --> 00:14:23.420 Yeah. 00:14:24.300 --> 00:14:24.680 That's. 00:14:25.340 --> 00:14:26.040 Is that him? 00:14:26.140 --> 00:14:26.680 That's where he's got it. 00:14:26.880 --> 00:14:27.480 Yeah, that's him. 00:14:27.560 --> 00:14:28.100 Nice. 00:14:28.560 --> 00:14:28.640 Cool. 00:14:29.660 --> 00:14:32.200 You've even got your animated Zoom. 00:14:32.680 --> 00:14:32.940 Oh, yeah. 00:14:33.000 --> 00:14:34.580 It's got the codex as well. 00:14:34.720 --> 00:14:35.000 I'm going to stroll. 00:14:35.400 --> 00:14:36.500 Unified experience for your terminal. 00:14:36.520 --> 00:14:36.840 Nice. 00:14:37.220 --> 00:14:37.340 Nice. 00:14:37.360 --> 00:14:43.140 Yeah, so this is, I don't know how this relates back to Toads, but it must in ways that I don't 00:14:43.200 --> 00:14:43.280 know. 00:14:43.740 --> 00:14:44.000 Well done. 00:14:44.200 --> 00:14:45.160 Well done, Will. 00:14:46.780 --> 00:14:47.640 It was the inkblot. 00:14:47.800 --> 00:14:48.400 What do you see here? 00:14:48.540 --> 00:14:49.140 I see a Toad. 00:14:49.920 --> 00:14:50.160 Exactly. 00:14:50.980 --> 00:14:55.540 Well, I want to talk about something that sort of AI related as well. 00:14:56.060 --> 00:15:01.280 So FastAPI just made, I'm linking to a merge request, 00:15:01.680 --> 00:15:04.320 and we'll link to the actual page too. 00:15:04.780 --> 00:15:08.540 But in the contributing to FastAPI page, 00:15:09.160 --> 00:15:12.940 there was a new change to talk about contribution instructions 00:15:13.260 --> 00:15:18.500 about LLM generated code and comments and automated tools for PRs. 00:15:18.840 --> 00:15:33.100 So I'm guessing that all FastAPI at least, but probably all very popular projects are having a problem with people doing PRs that they really haven't spent that much time on the PR, but they want to get their name in or something. 00:15:33.220 --> 00:15:33.600 I don't know. 00:15:35.040 --> 00:15:37.900 But there's some really good highlight here. 00:15:37.960 --> 00:15:49.460 And it's not, so I'm bringing this up not just because of FastAPI is awesome, and it is, but it's just sort of an interesting thing that we're having these sort of discussions. 00:15:49.960 --> 00:15:57.300 And this is a nice, concise verbiage if you want to add some of this pros to your own project to say what is allowed and what's not. 00:15:58.339 --> 00:16:05.900 And it's, so we'll link to the contributing guideline, developing, contributing, and there's an automated code and AI section. 00:16:06.980 --> 00:16:19.940 And the gist is you're encouraged to use AI tools to do things, you know, whatever tools you have at hand to do things efficiently, but also know that there is human effort on the other end for the pull request. 00:16:20.680 --> 00:16:28.440 And they just basically want to make sure that you're not doing less effort than they have to do to just check it. 00:16:28.640 --> 00:16:31.080 So please put a person in the middle. 00:16:31.580 --> 00:16:40.420 So there's things like they will automatically, they will close things that look like automated pull requests from bots and whatever. 00:16:41.780 --> 00:16:46.880 And there is a, there's, they have a section on human effort denial of service. 00:16:47.260 --> 00:16:58.220 You know, using automated tools and AI to submit PRs or comments that we have to carefully review and handle would be an equivalent of a denial of service attack on our human effort. 00:16:58.720 --> 00:17:04.120 be very little effort for a person submitting the pr that generates a large amount of effort on our 00:17:04.280 --> 00:17:10.540 side please don't do that um so i think this is uh completely fair and it said uh we will block 00:17:10.839 --> 00:17:17.660 accounts that spam us with repeated automated prs or comments use tools wisely and a nice um nice 00:17:17.939 --> 00:17:24.879 i think what is this spider-man comment come quote uh with great power i mean tools comes great 00:17:24.900 --> 00:17:32.220 responsibility. So I just think this was good on their part to throw this in of, yes, use tools, 00:17:32.520 --> 00:17:36.160 but know that there's a human on the other side having to deal with it. 00:17:36.780 --> 00:17:42.400 Yeah. Keep it focused, right? Don't submit a 7,000 line PR and say, I made it better. 00:17:44.000 --> 00:17:49.240 There was probably some small little part that need changed and stay on target, right? 00:17:49.700 --> 00:17:54.860 Yeah. Now that you bring that up, it is very easy now to say, oh, I want to refactor 00:17:54.880 --> 00:17:59.420 this function to be a new, like even with, without AI, I want to refactor this function to be a new, 00:17:59.590 --> 00:18:05.040 a new function name. And it's going to change tons of code. That's still okay to do if it's focused, 00:18:05.180 --> 00:18:10.260 even if it hits like hundreds of files, if it's just that one thing, like separate those up so 00:18:10.400 --> 00:18:14.760 that, so that code reviewers can go, oh yeah, you just changed that function name. That's fine. But 00:18:14.760 --> 00:18:20.300 if you do that plus, oh, plus I, you know, formatted with black and plus I like, you know, 00:18:20.440 --> 00:18:21.840 optimize this one function. 00:18:22.260 --> 00:18:23.600 It's terrible to combine those together. 00:18:23.900 --> 00:18:24.840 And, you know, let's see. 00:18:24.900 --> 00:18:29.040 And AI, it's very common for it to just churn through that kind of stuff 00:18:29.300 --> 00:18:30.320 and generate a bunch of changes. 00:18:30.760 --> 00:18:36.040 The curl team actually has blocked all AI contributions, period, for the same reason. 00:18:36.340 --> 00:18:37.340 It's like, this is out of control. 00:18:37.400 --> 00:18:37.980 We're not doing it. 00:18:38.140 --> 00:18:41.740 I got a weird request for a private repository. 00:18:43.700 --> 00:18:50.400 When I was starting the pytest course, I kicked around the idea of having a GitHub group 00:18:50.420 --> 00:18:57.100 whatever like whatever those are uh organization for testing code um i decided not to but it's that 00:18:57.280 --> 00:19:02.100 or that or that like organization still has some of the private code i used for the course 00:19:02.520 --> 00:19:08.520 and i had somebody request me to give it clod access to my private notes no i'm not gonna do 00:19:08.700 --> 00:19:14.100 that um no but anyway i'll share one really quick weird clod plus github thing while we're on the 00:19:14.200 --> 00:19:19.240 topic then we'll move on um i am working on this project that i was doing something with clod code 00:19:19.260 --> 00:19:24.520 on this feature. And I created a GitHub issue with a lot of notes for myself about it on GitHub, 00:19:24.860 --> 00:19:29.000 but I didn't connect Claude code to it or anything. And then I was like, hey, Claude, 00:19:29.100 --> 00:19:32.760 let's just brainstorm about what it would look like in this code base to add this feature. 00:19:32.980 --> 00:19:38.360 And it takes a second that goes, I see that you've considered this, this, and this. And now that now 00:19:38.480 --> 00:19:43.840 that I've got that background, I think this I'm like, how do you know that? What it had done is I 00:19:43.800 --> 00:19:47.480 I had the GitHub, the GH CLI installed on my computer. 00:19:47.590 --> 00:19:50.460 And so it used GH to go explore the GitHub repository 00:19:50.740 --> 00:19:51.680 and find the issue. 00:19:52.160 --> 00:19:54.220 Issue 1,274 or something. 00:19:54.780 --> 00:19:57.220 Yeah, issue 1,274 said you wanted to do it this way. 00:19:57.220 --> 00:20:00.900 I'm like, okay, that is insane that it just got in there 00:20:00.900 --> 00:20:02.340 and I didn't ask it to, you know what I mean? 00:20:03.220 --> 00:20:03.660 Yeah, anyway. 00:20:04.660 --> 00:20:06.420 Do I want GH on my computer? 00:20:08.500 --> 00:20:09.940 I'm like, how did it figure that out? 00:20:09.990 --> 00:20:12.220 It shouldn't have access to that information, but it's okay. 00:20:12.620 --> 00:20:13.540 How about we move on? 00:20:13.800 --> 00:20:14.400 Extra time. 00:20:14.920 --> 00:20:15.020 Yeah. 00:20:15.760 --> 00:20:16.260 Do you have any extras? 00:20:16.700 --> 00:20:17.000 Yeah, sure. 00:20:17.020 --> 00:20:19.720 I got a couple, and then we can flip over to you. 00:20:20.020 --> 00:20:27.620 So first of all, remember, Henry Schreiner pointed out that you can use compiled bytecode as a flag to uv. 00:20:28.160 --> 00:20:37.440 And it points out in the uv docs here that uv does not compile PY files to bytecode in the Dunder PyCache startup PYC file. 00:20:37.580 --> 00:20:40.800 Instead, that is lazily done at module import. 00:20:41.420 --> 00:20:49.060 And that really got my attention because all of the Docker deployments that we do, for example, Python Bytes runs on Docker. 00:20:49.370 --> 00:20:52.600 So when I deploy a new version of Python Bytes.fm, what happens? 00:20:52.850 --> 00:20:59.800 It compiles the code, installs the dependencies with uv, and then it starts, you know, there's other stuff, but effectively, 00:21:00.070 --> 00:21:05.740 then it just starts Granian running Python Bytes, right, as a core to app. 00:21:06.000 --> 00:21:12.400 And from the time that it actually starts starting until it's all the way started, like the website is unavailable, right? 00:21:12.820 --> 00:21:12.900 Yeah. 00:21:13.040 --> 00:21:15.400 Because it's not some super complicated Kubernetes thing. 00:21:15.400 --> 00:21:16.840 It just restarts the Docker container. 00:21:17.400 --> 00:21:25.320 And for me, for the extra simplicity of like having one to two seconds of downtime per couple times a week is totally fine. 00:21:25.560 --> 00:21:42.120 But what I realized when Henry said that, and you talked about uv not compiling these things, that that actually means it's got to every time I start the Docker container, literally every time it has to compile the PYC files for every library that it uses. 00:21:42.270 --> 00:21:44.100 And it uses like well over 50. 00:21:44.260 --> 00:21:46.300 There's a lot of libraries for these web apps, right? 00:21:46.640 --> 00:21:46.720 Yeah. 00:21:46.860 --> 00:21:47.440 And I'm like, wow. 00:21:47.590 --> 00:21:47.740 Okay. 00:21:47.810 --> 00:21:53.280 So there's no scenario where it will ever not have to generate those on AppStart, right? 00:21:53.400 --> 00:21:55.400 because I don't ever shut down the Docker container 00:21:55.440 --> 00:21:56.100