WEBVTT 00:00:00.020 --> 00:00:04.960 Hello and welcome to Python Bytes, where we deliver Python news and headlines directly to your earbuds. 00:00:05.400 --> 00:00:09.660 This is episode 459, recorded November 24th, 2025. 00:00:10.400 --> 00:00:11.240 And I am Brian Okken. 00:00:11.480 --> 00:00:12.280 And I am Michael Kennedy. 00:00:12.660 --> 00:00:18.960 And we want to thank everybody that supports us through the stuff we sell to you guys 00:00:19.260 --> 00:00:23.900 and provide services like the courses at Talk Python Training, the Complete pytest course, 00:00:24.960 --> 00:00:26.780 our Patreon supporters, of course, we love you. 00:00:26.880 --> 00:00:30.220 and also like everybody that buys books and stuff. 00:00:31.600 --> 00:00:33.100 Connect with us if you'd like to, 00:00:33.270 --> 00:00:34.680 like to send us some topic ideas 00:00:35.000 --> 00:00:36.780 or have a comment about what we said on the show. 00:00:37.420 --> 00:00:38.420 Feel free to connect with us. 00:00:38.860 --> 00:00:43.459 There's a contact us form on pythonbytes.fm, 00:00:45.400 --> 00:00:47.860 but you can also reach us on Bluesky or Mastodon 00:00:48.360 --> 00:00:49.620 and those links are in the show notes. 00:00:50.000 --> 00:00:51.460 If you are listening to us 00:00:51.460 --> 00:00:54.939 and occasionally would like to maybe see what we look like 00:00:54.960 --> 00:00:58.220 or see the topics that we're putting on the screen, 00:00:58.510 --> 00:01:03.360 you can join us on YouTube at pythonbytes.fm/live. 00:01:03.720 --> 00:01:06.920 And there you can also subscribe to the show 00:01:07.030 --> 00:01:11.680 and also get notified when the upcoming ones are going on. 00:01:12.500 --> 00:01:15.100 Usually Monday at, we need to change this, 00:01:15.390 --> 00:01:16.240 usually Monday at 11, 00:01:16.640 --> 00:01:18.440 but all the older versions are there too. 00:01:18.880 --> 00:01:20.980 And if we ever change it for personal reasons, 00:01:20.980 --> 00:01:22.260 you can get notified there. 00:01:22.880 --> 00:01:24.800 And of course, please sign up for the newsletter. 00:01:24.840 --> 00:01:31.220 We love to send you all of the links of the things we talked about in the show are sent to you right to your inbox. 00:01:31.780 --> 00:01:33.040 And we don't spam you. 00:01:33.160 --> 00:01:34.500 It's just the show notes, really. 00:01:35.220 --> 00:01:36.720 What do you got for us up first, Michael? 00:01:36.920 --> 00:01:38.860 Actually, we have some pre-topics. 00:01:39.760 --> 00:01:42.180 We have a topic zero topic. 00:01:42.420 --> 00:01:43.080 How about that? 00:01:43.420 --> 00:01:43.540 Yeah. 00:01:43.740 --> 00:01:44.200 Topic zero. 00:01:44.440 --> 00:01:45.880 So I don't know if people notice. 00:01:46.500 --> 00:01:53.240 I mean, if you've read your email or listened to the radio or anything like that, you might know that it is the week of Black Friday. 00:01:53.480 --> 00:01:57.720 And I think there's a lot of restraint on our end, Brian, by keeping it to the week. 00:01:57.960 --> 00:02:01.840 Like I was getting Black Friday sales in October and this is wrong. 00:02:02.160 --> 00:02:05.060 This is disrespecting Halloween amongst other things. 00:02:05.340 --> 00:02:05.580 Yeah. 00:02:06.700 --> 00:02:10.479 Anyway, Black Friday, I launched the Black Friday sale over at Talk Python. 00:02:10.520 --> 00:02:11.980 And this year is different than the last year. 00:02:12.260 --> 00:02:15.380 Traditionally, I just sort of done, hey, get the everything bundle, get all the courses 00:02:16.060 --> 00:02:16.840 on in forever sort of thing. 00:02:17.280 --> 00:02:19.380 But I wanted to do a couple of different deals. 00:02:19.580 --> 00:02:21.900 So now there's three options you can pick from. 00:02:21.960 --> 00:02:27.720 you can pick i have what's called the ai python bundle so two of our most popular courses agentic 00:02:27.760 --> 00:02:34.300 ai programming with python the one that i wrote and that's if you want to use things like water 00:02:34.560 --> 00:02:41.240 cursor or junior or whatever to build applications with alongside you and we have llm building blocks 00:02:41.240 --> 00:02:48.559 in python by vincent mormonam which is uh basically if i'm going to build something that uses an llm 00:02:48.680 --> 00:02:52.800 as an API kind of really cool stuff in both courses they're both really well reviewed and 00:02:53.000 --> 00:02:57.960 received you can get that for like half off as a special mini bundle then the whole library thing 00:02:58.060 --> 00:03:02.900 is still on you can get it at at super discounts and I'm also offering the talk python in production 00:03:03.080 --> 00:03:08.340 book it's doing really well for a while it's been a good while at number one in software engineering 00:03:08.600 --> 00:03:14.960 on Amazon which is amazing it's nice it's got pure five star reviews on gumroad at least as of 00:03:14.940 --> 00:03:19.240 yesterday. I haven't looked today, but I think that's still true. So really well received. 00:03:19.480 --> 00:03:24.040 That's also on sale at a discount. So that's Black Friday at Talk Python. talkpython.fm 00:03:24.240 --> 00:03:31.060 slash Black-Friday. Check it out, please. It's, as you said, at the top brain, it's a really 00:03:31.140 --> 00:03:34.280 great way to support a show. Make sure that we keep doing what we're doing here on the podcast. 00:03:34.960 --> 00:03:40.320 And with that, how about you? Well, I was actually not planning on doing a Black Friday thing, 00:03:40.440 --> 00:03:45.680 but I saw your topic in there. So I thought, yeah, why not? I'll do a Black Friday thing too. 00:03:46.280 --> 00:03:51.600 So the complete pytest course bundle, I put that on sale. And if you go, so you have to use a coupon 00:03:51.820 --> 00:03:57.820 code, the coupon code, if you go to the, if you just say, yeah, I want to get this. If you type 00:03:57.860 --> 00:04:04.759 in Black Friday, hit apply, then it's a 20% discount. But yeah, I don't think that looks 00:04:04.780 --> 00:04:10.760 big enough um i think i think we'll also do a save 50 so if you do save 50 um and apply that 00:04:11.140 --> 00:04:16.720 that's better that's 29 bucks now um so you get half off um 20 off or half off your choice 00:04:18.479 --> 00:04:24.820 um so uh doing that it'll be in the show notes uh but i kind of want okay so i was trying to match 00:04:25.100 --> 00:04:29.080 michael because he was doing 20 on some of the stuff so i did i did the black friday for 20 00:04:28.980 --> 00:04:39.220 But then I read my newsletter from Pragmatic, and Pragmatic is doing a 50% off for Black Friday. 00:04:39.320 --> 00:04:42.980 So you can get all Pragmatic books. 00:04:43.320 --> 00:04:45.520 If you save 50, you get 50% off. 00:04:45.720 --> 00:04:47.880 And that includes Python testing with pytest. 00:04:48.160 --> 00:04:52.160 So you can grab the video course or the book or both. 00:04:53.040 --> 00:04:55.440 So those are my Black Friday deals. 00:04:55.780 --> 00:04:56.020 Awesome. 00:04:56.100 --> 00:05:09.020 And yeah, I don't, I mean, I know sometimes it feels overly salesy, but I did not do Black Friday one year and I got a ton of email like, Michael, where's your Black Friday sales? I've been hoping that you would do one. So I know at least a subset of people genuinely look forward to it. 00:05:09.120 --> 00:05:15.980 And I personally, if there's something I really want for my learning path, I try to get it whenever I get it. 00:05:16.979 --> 00:05:20.160 But there's some things that are like, it depends on your budget. 00:05:20.270 --> 00:05:24.160 And there's some things that I don't need to have right away and I'd like to use. 00:05:24.160 --> 00:05:28.120 And there's a lot of stuff that I've purchased on Black Friday sales. 00:05:28.420 --> 00:05:35.980 And I appreciate that independent retailers and independent people like you and me do the Black Friday thing. 00:05:36.280 --> 00:05:40.980 people that the full price is just a smidge out of their price range that's good yeah absolutely 00:05:41.660 --> 00:05:45.360 all right let's talk about python stuff i mean that was python stuff but you know other stuff 00:05:45.590 --> 00:05:52.620 yeah pure python and i'm talking a language level python okay there's a lot more to python than just 00:05:52.700 --> 00:05:57.900 the language i think some people get confused i saw this comment on reddit of all places somebody 00:05:57.950 --> 00:06:02.300 said hey what podcast should i listen to to learn python like why would you do that that's stupid 00:06:02.410 --> 00:06:06.240 why would you listen to a podcast like just it's a simple language just go here and take the 00:06:06.260 --> 00:06:07.660 I was like, a little bit broader. 00:06:07.810 --> 00:06:10.320 But today, no, actually, we're talking built-ins. 00:06:10.370 --> 00:06:11.140 We're talking runtime. 00:06:13.479 --> 00:06:18.880 So PEP 814, this one is a really natural addition now that Python 3.14 came out. 00:06:19.380 --> 00:06:22.480 This is add frozen dict as a built-in type. 00:06:22.920 --> 00:06:26.880 Comes from Victor Stinner, who does a ton of performance stuff as a core developer. 00:06:27.300 --> 00:06:28.020 Thank you for that, Victor. 00:06:28.500 --> 00:06:34.920 And the idea is that when you have a frozen type, you get a lot of guarantees that you 00:06:34.860 --> 00:06:40.020 can work against that make your life easier, your bugs, et cetera, right? With a regular dictionary, 00:06:40.150 --> 00:06:43.520 you might say, oh, I need to return this dictionary to a thing. And you don't do a copy, 00:06:43.640 --> 00:06:47.060 you just hand it over. And then somebody changes it. You're like, wait, you aren't supposed to 00:06:47.180 --> 00:06:51.280 change it. I'm just trying to give you some data, right? So these frozen types are great for if you 00:06:51.380 --> 00:06:55.480 don't want something to change, it's not going to change. Also, in the code that would try to change 00:06:55.490 --> 00:06:58.820 it would get an error, right? So you're like, no, you're not supposed to do this. Figure something 00:06:58.910 --> 00:07:02.840 else out, right? The intention is sort of conveyed through the exceptions, I guess, of a cause. 00:07:03.560 --> 00:07:07.800 But also, it's really good for concurrency, which is the link back to 3.14. 00:07:08.300 --> 00:07:12.880 Now that we have true parallelism, we, I don't know how many people are doing this, 00:07:13.060 --> 00:07:17.980 but find yourself a re-entered lock and use it in your code if you're writing true parallel code, right? 00:07:18.060 --> 00:07:22.800 Because race conditions, deadlocks, well, it starts with race conditions, ends with deadlocks, and hopefully fix. 00:07:23.620 --> 00:07:26.940 Anyway, you want to do that, and you've got to lock mutable code. 00:07:26.940 --> 00:07:30.480 But if you're reading, two things are reading from the same data structure, and it's not changing, 00:07:30.900 --> 00:07:32.040 well, there ain't no problem with that. 00:07:32.180 --> 00:07:35.980 You can read with a hundred threads in parallel and they're all going to get the same answers 00:07:36.620 --> 00:07:37.840 deterministically, right? 00:07:37.890 --> 00:07:43.680 So having frozen dict adds dictionaries in as a type that is basically purely thread safe 00:07:43.790 --> 00:07:45.980 if you use a frozen dict instead of a regular one. 00:07:46.180 --> 00:07:46.460 Cool, right? 00:07:46.700 --> 00:07:47.240 That is cool. 00:07:47.490 --> 00:07:51.200 I wonder if this will ripple up into other data types like classes and stuff. 00:07:51.440 --> 00:07:52.740 That is a very good question. 00:07:53.000 --> 00:07:54.480 So I have an answer for you as well. 00:07:54.860 --> 00:07:55.920 So there's some interesting things. 00:07:56.110 --> 00:07:57.660 I linked to the discussion, not the pep. 00:07:57.810 --> 00:08:01.780 And there's like a really thoughtful conversation by lots of people that you know from the show. 00:08:01.960 --> 00:08:04.140 It's like, well, okay, that's cool. 00:08:04.540 --> 00:08:07.740 Can I equate a dictionary with a frozen dict? 00:08:08.120 --> 00:08:13.100 Because what you'll see from the PEP is frozen dict actually derives from something that is not a dictionary. 00:08:13.350 --> 00:08:16.740 So it's not, if you said, is instance a dictionary frozen dict, it would say no. 00:08:17.400 --> 00:08:20.520 I'm not so sure how I feel about that, but that's how it is. 00:08:20.860 --> 00:08:22.760 So the question is, well, can you say equal, equal? 00:08:23.560 --> 00:08:25.120 And is it ordered and so on? 00:08:25.130 --> 00:08:28.480 It is ordered, but is that order dependent and the equals and so on, right? 00:08:28.670 --> 00:08:30.360 So there's a lot of stuff coming along. 00:08:30.600 --> 00:08:32.440 And here you can go see all the conversation there. 00:08:32.700 --> 00:08:35.520 So I also, just like you, Brian, like, well, what else is frozen in Python? 00:08:35.719 --> 00:08:36.860 Like, what do we already have? 00:08:37.000 --> 00:08:38.360 You know, if we didn't have a frozen dictionary. 00:08:39.200 --> 00:08:43.500 So I put together a list of existing frozen types and structures in Python. 00:08:44.300 --> 00:08:45.420 Tuple, frozen set. 00:08:45.600 --> 00:08:47.440 Frozen set was the motivation for frozen dict. 00:08:47.480 --> 00:08:50.000 Like, well, if we got a frozen set, why can't we have a frozen dictionary? 00:08:50.300 --> 00:08:50.700 You know what I mean? 00:08:51.200 --> 00:08:53.820 String, obviously, bytes, ranges, memory views. 00:08:54.220 --> 00:08:58.140 Memory views are interesting to put over like a buffer, but you don't want it to be written to. 00:08:58.540 --> 00:09:05.640 but you've also got mapping proxy types you've got a record class in the form of data classes 00:09:05.920 --> 00:09:09.760 and then data classes you can say frozen is true so this is as close as you're going to get probably 00:09:09.860 --> 00:09:17.360 to what you're asking for right frozen classes you technically could more or less do that if you had 00:09:17.480 --> 00:09:22.260 private variables and only read-only properties but that's a lot of work you might as well just 00:09:22.440 --> 00:09:26.240 create a frozen data class i don't know but yeah so there's a whole bunch of stuff that i put in 00:09:26.220 --> 00:09:28.080 here that people can check out. 00:09:28.120 --> 00:09:31.480 I put a little extra data sheet because I'm like, huh, 00:09:31.800 --> 00:09:32.700 I also want to know this. 00:09:33.240 --> 00:09:33.640 Yeah. 00:09:34.020 --> 00:09:34.860 Yeah. All right. 00:09:35.260 --> 00:09:38.080 I'm looking forward to Python 3.15 being more frozen. 00:09:38.200 --> 00:09:38.580 How about that? 00:09:39.100 --> 00:09:40.040 More frozen. Yeah. 00:09:40.340 --> 00:09:41.100 More frozen. 00:09:41.360 --> 00:09:42.340 Might be faster too. 00:09:42.620 --> 00:09:44.980 Yeah. It definitely has a possibility for faster, 00:09:45.300 --> 00:09:46.200 safer code more easily. 00:09:46.760 --> 00:09:47.040 Yeah. 00:09:47.180 --> 00:09:47.660 Document it though. 00:09:48.120 --> 00:09:49.100 Yeah, got to document it. 00:09:49.720 --> 00:09:54.880 I'm bringing up an interesting topic that this was suggested by John Hagen. 00:09:55.120 --> 00:09:55.420 Thanks, John. 00:09:56.640 --> 00:09:57.540 Material for MakeDocs. 00:09:57.820 --> 00:10:01.320 So I use MakeDocs and I use Material for MakeDocs. 00:10:01.440 --> 00:10:04.460 Material for MakeDocs is a theme for MakeDocs, 00:10:04.460 --> 00:10:07.120 but it also adds some cool stuff to it. 00:10:07.270 --> 00:10:09.820 So it's like a theme++ or something. 00:10:11.800 --> 00:10:17.080 And I use it for both personal projects and for at work 00:10:17.880 --> 00:10:20.140 because it's just as easy to work with. 00:10:20.200 --> 00:10:22.020 Anyway, there's some news about Material. 00:10:22.360 --> 00:10:26.740 So the news that came out is that the team behind it 00:10:26.790 --> 00:10:32.280 is putting the Material for MakeDocs project in maintenance mode. 00:10:32.720 --> 00:10:38.020 So for new updates, I don't know because I didn't really fully read this, 00:10:40.400 --> 00:10:44.700 but I'm guessing that they're going to, let's see, changes the issue tracker. 00:10:46.620 --> 00:10:49.160 Are they encouraged to open bug reports following? 00:10:49.700 --> 00:10:52.820 okay, they'll fix critical bugs and security vulnerabilities. 00:10:53.320 --> 00:10:53.680 That's right. 00:10:53.860 --> 00:10:55.160 That's a good, that's fair. 00:10:56.200 --> 00:10:58.260 Because a lot of people use it, including me. 00:10:58.900 --> 00:10:59.640 So I care about that. 00:11:00.020 --> 00:11:02.620 But why are they putting it in maintenance mode? 00:11:02.800 --> 00:11:04.820 It's because the efforts that they're putting in this, 00:11:04.940 --> 00:11:08.140 they're switching over to a new project called Zensical. 00:11:09.600 --> 00:11:10.040 Zensical? 00:11:10.380 --> 00:11:11.860 Anyway, interesting name. 00:11:12.480 --> 00:11:15.500 Modern static site generator built on material for MakeDocs team, 00:11:15.780 --> 00:11:17.380 built by the material for MakeDocs team. 00:11:17.600 --> 00:11:27.380 So it's a backwards compatibility, and we're going to link to a post that is actually all the, it's like a four post series talking about the transition because it affects a lot of people. 00:11:27.980 --> 00:11:41.020 So they're transforming Material for MakeDocs, they're starting Zensical, and they've got a Material for MakeDocs insiders program, and they're closing down GitHub discussions on Material for MakeDocs. 00:11:41.960 --> 00:11:47.820 So it doesn't seem like it's profit-driven 00:11:48.120 --> 00:11:49.700 because they were actually making a decent amount 00:11:49.730 --> 00:11:53.240 off of GitHub sponsorships for this, 00:11:53.920 --> 00:11:54.960 but maybe that's part of it. 00:11:55.180 --> 00:11:57.600 But the gist of it is at the top, 00:11:57.740 --> 00:12:00.080 they said they want Zensical 00:12:00.340 --> 00:12:03.360 to overcome technical limitations of MakeDocs. 00:12:03.620 --> 00:12:05.400 There's so many people that were using it, though, 00:12:05.580 --> 00:12:07.600 and not using any other form of MakeDocs, 00:12:07.740 --> 00:12:11.139 but in part of this discussion they were talking about 00:12:11.180 --> 00:12:19.960 that a lot of the stuff in the forum and a lot of stuff in just GitHub issues were really not their problem. 00:12:20.380 --> 00:12:25.880 There were like really issues with MakeDocs or issues with some other dependencies that they were using. 00:12:26.010 --> 00:12:28.440 So Zensical is going to just wrap up. 00:12:29.080 --> 00:12:33.540 It's going to be a replacement for MakeDocs and MakeDocs, material for MakeDocs. 00:12:33.800 --> 00:12:47.080 And I think a few of the other plugins that used to work with all of this, they're pulling those in to have a support model so that they can actually support everything that matters to people that use it. 00:12:48.420 --> 00:12:52.100 The new website, Zensical.org, is just fun to look at. 00:12:52.680 --> 00:12:54.240 There's this cool animation thing. 00:12:56.900 --> 00:12:58.440 Yeah, it's really cool. 00:12:58.530 --> 00:13:00.200 So for people listening, you got to check it out. 00:13:00.360 --> 00:13:01.120 Zensical.org. 00:13:01.380 --> 00:13:08.420 It's a black background with this kind of a yellow light laser thing going around in circles. 00:13:09.860 --> 00:13:11.340 I don't know what that shape is. 00:13:12.120 --> 00:13:12.600 Like a donut. 00:13:15.240 --> 00:13:16.860 Thank you, Henry Schreiner. 00:13:17.760 --> 00:13:19.440 It's also a... 00:13:20.420 --> 00:13:21.520 Henry jumped in the show. 00:13:21.840 --> 00:13:24.500 It's also a rust rewrite, and it's five times faster. 00:13:25.000 --> 00:13:25.860 So a lot faster. 00:13:26.760 --> 00:13:28.360 I'm pretty excited to try that out. 00:13:28.420 --> 00:13:36.020 I haven't tried this yet, but since I'm a heavy material for MakeDocs user, I'll definitely be checking this out. 00:13:36.800 --> 00:13:44.920 So one of the things I was curious about is the whole, like, how does this work for, like, is it going to go away or what's the open source model? 00:13:45.400 --> 00:13:49.760 It's still going to be open source and MIT licensed. 00:13:50.400 --> 00:13:52.520 And there's a compatibility back. 00:13:52.880 --> 00:13:54.340 They're trying to make it backwards compatible. 00:13:54.420 --> 00:13:58.980 So when you switch over, you can use your make ducks YAML file just as is. 00:13:59.300 --> 00:14:00.060 And hopefully it works. 00:14:00.140 --> 00:14:01.000 I haven't tried this yet. 00:14:01.260 --> 00:14:04.000 And I, you know, I actually haven't like customized it too much. 00:14:04.120 --> 00:14:05.740 So it's probably going to work fine for me. 00:14:06.580 --> 00:14:11.460 But I do want to check out this, this compatible backwards compatibility thing to switch it over. 00:14:11.860 --> 00:14:16.740 I like some of the cool features that they're, they're trying to build in and faster is great. 00:14:17.860 --> 00:14:22.020 The other, the other thing I was, so how are they making money? 00:14:22.160 --> 00:14:24.120 is the Zensical Spark model. 00:14:24.620 --> 00:14:25.940 So this is going to be, 00:14:26.620 --> 00:14:28.160 so what's Zensical Spark? 00:14:29.440 --> 00:14:30.560 It's for basically, 00:14:31.260 --> 00:14:33.240 actually, I think it's more than this, 00:14:33.280 --> 00:14:36.780 but part of it is companies that use it 00:14:37.080 --> 00:14:39.060 or groups, teams that use it, even startups. 00:14:39.460 --> 00:14:41.120 It's not just for enterprise people, 00:14:41.760 --> 00:14:46.000 but groups can go ahead and sign up for this 00:14:46.080 --> 00:14:47.440 and have better support model. 00:14:47.760 --> 00:14:50.280 So they can prioritize supporting people 00:14:50.460 --> 00:14:52.020 that are paying them, which makes sense. 00:14:52.320 --> 00:14:55.280 But those fixes will help everybody. 00:14:55.720 --> 00:14:56.120 So that's good. 00:14:57.460 --> 00:15:02.180 One of the cool things that they're doing also during the transition is material for 00:15:02.260 --> 00:15:08.140 MakeDocs, one of the ways they made money is they had both an open version that's just 00:15:08.200 --> 00:15:08.760 free for everybody. 00:15:09.180 --> 00:15:13.160 And then they would release new features to an insiders group. 00:15:13.460 --> 00:15:15.160 So you could get new features right away. 00:15:15.620 --> 00:15:19.620 And then they would sort of trickle into the general population features. 00:15:19.780 --> 00:15:25.100 they're getting um i don't know if there's going to be something similar for the spark thing but 00:15:25.400 --> 00:15:29.740 for material for make docs they've just opened up the floodgates anything that was in the insiders 00:15:29.820 --> 00:15:35.120 is now part of uh the open source thing so if you want to stick to that you get all the features 00:15:35.640 --> 00:15:43.280 so anyway just news for people that use make docs yeah nice i'm i'm optimistic here if their website's 00:15:43.400 --> 00:15:49.040 anything to go by no it's i'm optimistic i think it will it's the kind of thing that'll make it 00:15:49.020 --> 00:15:52.560 really polished and really nice if they get a decent number of customers. 00:15:52.730 --> 00:15:53.380 So good. 00:15:53.660 --> 00:15:59.120 And I do like that they're just actually putting the people on the people with their pictures. 00:15:59.470 --> 00:16:01.060 She just, these are the people behind it. 00:16:01.270 --> 00:16:07.460 It's not something just no faceless people making your money off you. 00:16:07.780 --> 00:16:08.260 Exactly. 00:16:08.770 --> 00:16:08.940 Cool. 00:16:09.220 --> 00:16:09.600 That's right. 00:16:09.980 --> 00:16:10.980 Keep Python independent. 00:16:11.110 --> 00:16:11.260 Okay. 00:16:11.960 --> 00:16:17.800 So I want to talk about something that was sent in to us by Gerber Decken. 00:16:18.340 --> 00:16:21.000 And this is sort of the hat trick, if you will, Brian. 00:16:21.400 --> 00:16:26.160 Two weeks ago, you talked about pip-dep-tree and UV-pip-tree, right? 00:16:26.520 --> 00:16:29.020 And then the last week, you talked about dep-tree. 00:16:29.899 --> 00:16:32.900 This time, I want to talk about a couple of things. 00:16:33.000 --> 00:16:34.620 I want to talk about uv. 00:16:35.520 --> 00:16:36.740 I mean, I got to look at this. 00:16:36.760 --> 00:16:38.980 This is a bit of a statement here. 00:16:39.200 --> 00:16:39.960 I know it's rough. 00:16:40.560 --> 00:16:42.000 Rough, analyze, graph. 00:16:42.500 --> 00:16:47.659 And you give it a virtual environment and some place to start or file 00:16:47.700 --> 00:16:52.740 or something like that. And it will generate basically an architectural layer diagram. 00:16:53.390 --> 00:16:59.180 This portion of your application depends on these other modules, which depend on those modules. And 00:16:59.540 --> 00:17:03.440 is there any form of circular weirdness or whatever, right? So if you want to understand 00:17:03.590 --> 00:17:09.180 how that works, this is like, it'll give you just a list. So this thing tech, which I'm covering, 00:17:09.250 --> 00:17:14.819 he sent in is a Python tool to visualize and enforce dependencies using this architecture. 00:17:14.839 --> 00:17:17.839 and it basically takes that output that I described 00:17:18.020 --> 00:17:20.260 and then turns it into a UI, okay? 00:17:20.680 --> 00:17:20.880 Okay. 00:17:21.199 --> 00:17:25.280 So there's a little graph that shows how it works, 00:17:25.329 --> 00:17:27.620 but basically you just create a TOML file 00:17:28.060 --> 00:17:30.220 and then you run a command and it will scheme your code. 00:17:30.640 --> 00:17:33.440 It will generate basically that, more or less, that output. 00:17:33.810 --> 00:17:37.380 And then you can upload that, not your code, 00:17:37.640 --> 00:17:40.060 just this little TOML file that basically has module names 00:17:40.110 --> 00:17:40.940 and nothing else in it, 00:17:41.500 --> 00:17:43.760 to this service that will turn that into a graph, okay? 00:17:43.880 --> 00:17:49.940 So I did that by creating one for a project that I'm not talking about yet, but I'm working on here. 00:17:50.330 --> 00:17:56.060 And you can see we've got this cool little thing and it shows like, how are you, how is it put together? 00:17:56.210 --> 00:17:57.740 What pieces depend on what, right? 00:17:57.900 --> 00:17:59.320 What depends on services? 00:17:59.450 --> 00:18:02.860 And then as you interact with it, you can click on like, I want to see what views depend upon. 00:18:03.100 --> 00:18:03.860 Oh, that's a lot. 00:18:04.360 --> 00:18:08.140 But if I click on view models, you can see there's a nice layered architecture, right? 00:18:08.280 --> 00:18:15.580 view models depend on services infrastructure modules and db models but it doesn't depend on 00:18:15.680 --> 00:18:20.000 the stuff above it that depends on it so you don't get these weird cycles and other things and there's 00:18:20.040 --> 00:18:24.820 like a little cms component it's used by the views it's used by the services and nothing else so you 00:18:24.880 --> 00:18:29.860 can get this like cool little understanding of different parts of your app what do you think 00:18:30.340 --> 00:18:36.299 this is cool so this is um maybe because we were talking about pipped up tree before this is not 00:18:36.380 --> 00:18:42.680 the third-party stuff is just this is your yeah this is your own code so how does your own code 00:18:42.760 --> 00:18:48.220 within itself like a set of sub modules depend upon each other because if you look at this um 00:18:48.540 --> 00:18:53.440 you actually look at the code this view model section probably has 30 or 50 classes in it 00:18:53.760 --> 00:18:59.520 this infrastructure bit has maybe 20 different things like utilities for web stuff urls and so 00:18:59.520 --> 00:19:04.840 on and text parsing and um numeric converting libraries and you know stuff like that this dv 00:19:04.800 --> 00:19:08.700 Everything has, I think, five database models and a helper class or something. 00:19:09.180 --> 00:19:10.720 But they just show up as these blocks. 00:19:10.880 --> 00:19:13.600 So you can kind of get a sense of like, how do these things interact? 00:19:14.180 --> 00:19:17.360 The lines are drawn by analyzing all the individual files, I believe, 00:19:17.920 --> 00:19:20.300 and seeing which ones point to things from other categories. 00:19:20.900 --> 00:19:22.200 Oh, nice. This is cool. 00:19:22.560 --> 00:19:24.940 Yeah. So I uploaded this picture. 00:19:25.900 --> 00:19:27.520 I shared this. I create these shareable graphs. 00:19:27.620 --> 00:19:29.740 So you can actually play with this graph yourself as well. 00:19:30.040 --> 00:19:33.340 Yes. And then Christian asks, is this unmaintained? 00:19:33.380 --> 00:19:37.600 Yes, I believe TAC has become unmaintained, but you can still run it. 00:19:37.610 --> 00:19:38.540 It still looks like it's okay. 00:19:38.820 --> 00:19:39.840 So that's a good point. 00:19:39.960 --> 00:19:46.280 I did notice after I put this together that somewhere it's got like a, although the GitHub 00:19:46.530 --> 00:19:51.140 repo, no, it's not TAC that is at least doesn't have an explicit statement that has gone into 00:19:51.260 --> 00:19:51.880 maintenance mode or anything. 00:19:52.640 --> 00:19:56.620 But if you look at TAC, it goes to gauge.sh. 00:19:56.640 --> 00:20:06.220 And if you go to gauge.sh, this product is changed and it's becoming some AI thing that means nothing to me. 00:20:07.180 --> 00:20:08.160 So I don't know. 00:20:08.360 --> 00:20:11.160 But I imagine they'll probably keep it running. 00:20:11.500 --> 00:20:13.740 And apparently it's also open source. 00:20:14.060 --> 00:20:16.380 So you could go and fork it and just run it yourself or whatever. 00:20:16.650 --> 00:20:16.920 I don't know. 00:20:17.230 --> 00:20:22.520 So there is some component in this whole chain that is, it's the visualization of it, not the parsing. 00:20:22.820 --> 00:20:25.240 I think TAC, which does the parsing, still works fine. 00:20:25.340 --> 00:20:26.480 but then it uploads the gauge. 00:20:26.570 --> 00:20:28.320 And the gauge thing is in question 00:20:28.630 --> 00:20:30.140 about whether that will still work. 00:20:30.660 --> 00:20:32.160 But, you know, you could always go 00:20:32.210 --> 00:20:33.800 and make yourself, you know, fork it. 00:20:34.180 --> 00:20:35.280 I mean, how hard would it be to make, 00:20:36.140 --> 00:20:38.500 given the file, which I don't have it easy, 00:20:38.560 --> 00:20:39.060 I can pull it up, 00:20:39.200 --> 00:20:40.900 but given a file that lists these relationships, 00:20:41.420 --> 00:20:42.620 how hard is it to graph it, right? 00:20:42.700 --> 00:20:44.420 You could AI your way to something 00:20:44.490 --> 00:20:46.340 that draws your pictures out of tech 00:20:46.990 --> 00:20:48.600 in like an afternoon if you really had to. 00:20:49.400 --> 00:20:51.800 This visualization left is an exercise for the reader. 00:20:52.140 --> 00:20:52.460 Exactly. 00:20:52.710 --> 00:20:53.799 Like you could visualize it 00:20:54.020 --> 00:20:57.020 if you knew the right series of prompts, I don't know, or you wanted to write it or something. 00:20:57.340 --> 00:21:00.460 No, anyway, that's a good point, Christian. Thank you. Over to you, Brian. 00:21:00.880 --> 00:21:08.400 Well, I wanted to talk about upcoming speedups in Python. So there's a couple news articles that 00:21:08.520 --> 00:21:15.280 came by that I noticed talking about some efforts to speed up Python in the future. So we're at 00:21:15.460 --> 00:21:22.300 Python 3.14 right now. 3.15 is in the works and 3.16 later, right? So one of the things, 00:21:22.400 --> 00:21:30.140 This is a post by Ken Jin, a plan for 5% to 10% faster free-threaded JIT by Python 3.16. 00:21:30.560 --> 00:21:36.480 And the highlight is 5% faster for 3.15, 10% faster for 3.16. 00:21:37.480 --> 00:21:42.060 And some of the names popped out as why I should pay attention to this. 00:21:42.600 --> 00:21:48.100 This was brought up during the Python Core Dev Sprint in Cambridge hosted by ARM. 00:21:48.860 --> 00:21:50.160 They planned this project. 00:21:50.520 --> 00:22:06.260 The planners of the project that were present is Savannah Ostrowski, Mark Shannon, Ken Jen, this person, Diego Russo, and Brent Butcher, accompanied by other CPython core team members as well. 00:22:07.620 --> 00:22:12.060 And also, I'm like, well, 5% to 10%, that's not that big of a deal. 00:22:12.400 --> 00:22:15.020 It says, you might wonder, 5% seems awfully conservative. 00:22:15.280 --> 00:22:18.520 However, note that this figure is a geometric mean. 00:22:18.540 --> 00:22:21.840 the number can range from slower to significantly faster. 00:22:22.210 --> 00:22:24.760 All numbers are high performance figures. 00:22:26.050 --> 00:22:29.080 So I think that means they're optimistically thinking 00:22:29.360 --> 00:22:30.960 it's going to be a lot faster. 00:22:32.880 --> 00:22:36.440 So it's interesting that the LLM involvement here 00:22:36.560 --> 00:22:37.160 is a little interesting. 00:22:37.880 --> 00:22:43.520 Plan for 3.15 profiling support via LLVM21. 00:22:43.800 --> 00:22:44.740 Oh, not LLVM. 00:22:44.740 --> 00:22:48.340 That's probably performance-driven compiler optimization. 00:22:48.400 --> 00:22:50.040 stuff. Yeah. Yeah. 00:22:50.350 --> 00:22:51.940 Where you profile it and then the 00:22:52.640 --> 00:22:54.260 compiler says let me look at the profiler 00:22:54.680 --> 00:22:56.340 output and then actually re-optimize 00:22:56.640 --> 00:22:58.340 based on how you actually ran. You know, like 00:22:58.350 --> 00:22:59.840 that sort of fact. I bet it's something like that. 00:23:00.260 --> 00:23:02.460 Yeah, but it's also looking forward to 00:23:03.180 --> 00:23:04.420 some support from 00:23:05.280 --> 00:23:06.400 LLVM20 and then LLVM21. 00:23:07.780 --> 00:23:08.500 So some 00:23:08.950 --> 00:23:10.540 of those lower 00:23:10.670 --> 00:23:12.140 level parsing improvements 00:23:12.550 --> 00:23:14.240 are going to help with the JIT. So 00:23:14.290 --> 00:23:15.980 trace recording, better machine code, 00:23:16.360 --> 00:23:18.660 Register allocation, top of stack caching, 00:23:19.140 --> 00:23:20.080 reference count elimination. 00:23:20.800 --> 00:23:21.660 That's an interesting one. 00:23:22.370 --> 00:23:25.380 More constant promotion and basic free threading support. 00:23:26.480 --> 00:23:30.180 So I'm looking forward to seeing there's some graphs 00:23:30.430 --> 00:23:33.480 and some more information that's really above my pay grade. 00:23:35.620 --> 00:23:36.500 That just- 00:23:36.500 --> 00:23:37.940 Bars and stuff, they must be in things. 00:23:37.940 --> 00:23:39.580 We don't know. 00:23:39.580 --> 00:23:41.000