WEBVTT 00:00:00.020 --> 00:00:05.580 Hello and welcome to Python Bytes, where we deliver Python news and headlines directly to your earbuds. 00:00:06.020 --> 00:00:10.900 This is episode 468, recorded February 2nd, 2026. 00:00:11.960 --> 00:00:12.580 I'm Michael Kennedy. 00:00:12.950 --> 00:00:13.640 And I'm Brian Ecken. 00:00:13.980 --> 00:00:15.600 This episode is brought to you by us. 00:00:16.260 --> 00:00:23.000 Brian's books, his new Lean TDD book, which you can get right now and is in development, but almost done. 00:00:23.320 --> 00:00:23.440 Yes. 00:00:24.600 --> 00:00:26.080 He's going to be done this week, folks. 00:00:26.240 --> 00:00:26.640 Don't worry about it. 00:00:28.020 --> 00:00:30.780 My Python and production book has been going strong as well. 00:00:30.900 --> 00:00:31.560 That's really fun one. 00:00:31.880 --> 00:00:35.360 And of course, our courses, all the links for those things are in the show notes. 00:00:35.940 --> 00:00:38.400 Follow us on the socials, sign up for the newsletter. 00:00:38.880 --> 00:00:39.740 We don't spam you. 00:00:39.830 --> 00:00:44.240 We just send you updates about the, about the episodes, extra information, 00:00:44.480 --> 00:00:48.000 more links, that kind of thing, as well as a periodic announcement of like, Hey, 00:00:48.200 --> 00:00:51.240 we've got a new course or a new book or whatever it is we're up to, you know, 00:00:51.420 --> 00:00:52.860 things like that, but we don't give it away. 00:00:53.290 --> 00:00:54.080 We don't sell it. 00:00:54.440 --> 00:00:54.920 Things like that. 00:00:55.080 --> 00:01:01.260 And with that, like a bolt of lightning striking out of the blue, what do we got? 00:01:01.920 --> 00:01:03.600 Well, we've got Django Bolt. 00:01:04.830 --> 00:01:12.420 So Django Bolt is actually, I learned about Django Bolt because I was looking at the Django 00:01:12.640 --> 00:01:18.700 chat website and or the Django chat and they had a, they had an episode building a Django 00:01:18.980 --> 00:01:23.480 API framework faster than FastAPI, which of course I was interested in. 00:01:24.000 --> 00:01:27.920 And so this episode actually discusses Django Bolt. 00:01:29.519 --> 00:01:35.100 And Django Bolt is a Rust powered behind the scenes, 00:01:35.250 --> 00:01:36.280 but it's inspired. 00:01:36.580 --> 00:01:37.900 It's a, so it's like fast, 00:01:39.120 --> 00:01:40.640 like we already have Django Rust framework 00:01:40.900 --> 00:01:41.760 and there's Django Ninja, 00:01:42.370 --> 00:01:46.200 but this is along those lines of trying to get 00:01:46.970 --> 00:01:48.460 an API framework for Django. 00:01:49.340 --> 00:01:50.760 The inspiration is kind of interesting. 00:01:51.540 --> 00:01:53.780 I think down near the bottom. 00:01:54.520 --> 00:01:58.040 There's inspired by, oh, inspired by Django REST framework, 00:01:58.340 --> 00:02:00.480 FastAPI, Litestar, and Robin. 00:02:00.920 --> 00:02:04.760 Apparently some of the Rust Python, 00:02:05.979 --> 00:02:07.740 the integrating Rust and Python 00:02:08.100 --> 00:02:09.880 was inspired by some of the Robin project. 00:02:10.000 --> 00:02:11.780 I don't know anything about Robin, actually. 00:02:12.140 --> 00:02:19.040 So interesting, different take on APIs for Django. 00:02:19.740 --> 00:02:30.420 And one of the things that was really interesting, especially in the discussion on the podcast, was the timing of it, trying to figure out how fast things are. 00:02:30.500 --> 00:02:33.600 And there's issues with that. 00:02:33.600 --> 00:02:39.040 But apparently he used a ton of graphs, a ton of charts, so you can look at what's going on. 00:02:39.480 --> 00:02:49.620 Also, in the act of doing that, realize that even Django REST framework, if you configure things in a certain way, you can do off-the-shelf things. 00:02:49.640 --> 00:02:51.440 things and get it pretty fast anyway. 00:02:52.220 --> 00:02:54.740 But so this is an interesting take. 00:02:55.210 --> 00:02:57.120 So there's a bunch of leaks we're going to link to. 00:02:57.300 --> 00:03:00.280 There's the Django Bolt repository. 00:03:00.780 --> 00:03:03.460 The documentation is set up and it's pretty good. 00:03:03.630 --> 00:03:05.100 Oh, I should back up. 00:03:05.280 --> 00:03:09.800 There's a little warning in it that it's still in progress. 00:03:10.560 --> 00:03:11.900 It's under active development. 00:03:12.260 --> 00:03:13.320 So be aware of that. 00:03:13.620 --> 00:03:15.900 OK, then there's the podcast episode. 00:03:16.440 --> 00:03:27.660 And then just recently, somebody came out with a video walking through using Django Bolt, which is an interesting discussion. 00:03:28.540 --> 00:03:31.460 And I actually just watched the first part of it. 00:03:31.470 --> 00:03:38.420 The first part of it actually talks about some of the ecosystem around APIs in Django and then walking through a little bit of it. 00:03:38.600 --> 00:03:42.240 So pretty interesting take on APIs. 00:03:42.720 --> 00:03:43.740 Yeah, that is super interesting. 00:03:44.640 --> 00:03:46.020 I've been looking at Django Bolt as well. 00:03:46.100 --> 00:03:50.900 it's not because I plan to use it because my websites are not in Django but just it's got 00:03:50.900 --> 00:03:56.540 some really interesting ideas out there and yeah also note on the performance thing do your own 00:03:56.740 --> 00:04:00.840 performance testing put stuff I think it's more the more importantly people should think about this 00:04:01.340 --> 00:04:07.060 as side by side like three or four weeks ago when I did my Python numbers everyone should know 00:04:07.400 --> 00:04:13.180 every Python developer should know people said well you did this on a m4 pro cpu and it's not 00:04:13.200 --> 00:04:17.799 going to be the same when you run it on a five dollar crappy server in the cloud i'm like true 00:04:18.260 --> 00:04:22.120 but if i run it on a five dollar server the people go well it doesn't run that's not comparable to my 00:04:22.500 --> 00:04:27.780 high-end server or whatever right like it's more like okay this one is relative to that this is 00:04:27.860 --> 00:04:32.820 like 2x of that other one or something right so just keep that in mind right yeah i mean numbers 00:04:32.980 --> 00:04:38.940 are tested on right but also i mean as long as the numbers are relatively tested you're doing 00:04:39.340 --> 00:04:45.980 you're doing a and b on the same hardware now there there might be differences in the um the 00:04:46.260 --> 00:04:53.220 the behind the c the c python implementation based on different hardware and to the point where one 00:04:53.600 --> 00:04:58.220 technique will work better on some platform than another but i don't think a lot of people are 00:04:58.540 --> 00:05:05.080 thinking in the dirt that much but anyway yeah yeah uh one quick bit of real-time follow-up from 00:05:05.020 --> 00:05:05.920 and posts in the audience. 00:05:06.220 --> 00:05:07.360 My first job was in Django. 00:05:07.520 --> 00:05:09.840 I always loved Django ORM plus migrations framework 00:05:10.040 --> 00:05:12.960 and Django Bolt connects ORM with fast async stuff, 00:05:13.120 --> 00:05:14.020 which is really cool indeed. 00:05:14.220 --> 00:05:15.840 Yeah, it seems like a neat project. 00:05:16.360 --> 00:05:17.840 Yeah, it'll be something to watch. 00:05:18.180 --> 00:05:20.180 Indeed, but did he mention async? 00:05:21.500 --> 00:05:25.260 What if you had leaks in your async code? 00:05:25.900 --> 00:05:28.140 So I want to talk about this thing called PyLeak. 00:05:28.400 --> 00:05:33.600 So PyLeak detects leaked async tasks, threads, 00:05:34.100 --> 00:05:41.560 event loop blocking. So that's not exactly a leak, but it's kind of a leak. So it's non-async code 00:05:41.680 --> 00:05:46.300 leaking into async sections. When I first saw this, I thought it was a memory diagnosing thing, 00:05:46.430 --> 00:05:52.800 but what it's for is diagnosing async tasks that if you've ever seen like this, this task was not 00:05:52.900 --> 00:05:58.520 awaited or something like that. And it's got a really nice programming model, but this is, 00:05:59.000 --> 00:06:00.640 This is something that certainly can happen. 00:06:01.060 --> 00:06:09.040 I will tell you if you run the ty or the Pyrefly typing integration with your editor and maybe 00:06:09.240 --> 00:06:14.760 PyCharm, I don't think PyCharm does this, but those two will put, PyCharm will detect 00:06:14.900 --> 00:06:19.180 that the stuff is not being treated right, but the others do inline type overlays. 00:06:19.660 --> 00:06:24.100 So you'll have like x equals some function call and you think x is an integer. 00:06:24.660 --> 00:06:28.640 If it says x and then in little gray, like it's not really in the code, but it's putting 00:06:28.660 --> 00:06:31.840 colon, coroutine of something, something int. 00:06:32.040 --> 00:06:33.860 You're like, oh, I forgot to await that. 00:06:34.720 --> 00:06:37.060 Because this is coming back as the unexecuted coroutine, 00:06:38.650 --> 00:06:40.860 not the number, the integer, right? 00:06:41.120 --> 00:06:43.900 That it's easy to do if you're writing regular async code, 00:06:44.020 --> 00:06:46.720 but it's really easy to do if what you're doing 00:06:47.260 --> 00:06:50.380 is converting a synchronous program to an async program. 00:06:50.900 --> 00:06:53.960 Because every call site of every function is synchronous, 00:06:54.150 --> 00:06:56.420 and then you go make those functions asynchronous, 00:06:57.070 --> 00:06:58.620 and then you try to go back and fix them 00:06:58.640 --> 00:06:59.300 everywhere you called them. 00:06:59.699 --> 00:07:02.600 It's not a syntax or a runtime error, usually, 00:07:02.840 --> 00:07:05.280 a lot of times, to actually not call that. 00:07:05.520 --> 00:07:06.160 It'll just run. 00:07:06.600 --> 00:07:07.720 So for example, if you have x, 00:07:08.340 --> 00:07:10.840 let's say x equals some function call. 00:07:11.200 --> 00:07:12.480 It normally gives you back a number, 00:07:12.560 --> 00:07:13.560 you wanna make sure it's not zero. 00:07:13.620 --> 00:07:16.320 So you'd say if x, if not x or if x, 00:07:16.440 --> 00:07:17.000 something like that, right? 00:07:17.240 --> 00:07:20.380 Well, when it's a coroutine, your if x still runs, 00:07:20.840 --> 00:07:21.640 it's just always true. 00:07:22.120 --> 00:07:22.940 And things like that, right? 00:07:23.340 --> 00:07:24.200 - Oh, yeah. - It's 'cause it's, 00:07:24.200 --> 00:07:25.620 is the coroutine falsy? 00:07:25.820 --> 00:07:27.979 No, there's only like five or six things 00:07:28.000 --> 00:07:29.760 and Python that are falsing and coroutine is not. 00:07:29.960 --> 00:07:30.860 So it's true, keep going. 00:07:31.240 --> 00:07:32.040 It's really sketch. 00:07:32.640 --> 00:07:34.500 So those are super hard to catch. 00:07:34.740 --> 00:07:35.900 And this is the kind of thing 00:07:36.180 --> 00:07:37.540 that theoretically will catch it. 00:07:37.860 --> 00:07:38.320 So pretty neat. 00:07:38.680 --> 00:07:41.600 Anyway, it depends how you start it, I believe. 00:07:42.020 --> 00:07:43.560 You've gotta do like a create task 00:07:43.660 --> 00:07:44.580 where the task has to be running. 00:07:44.700 --> 00:07:45.940 If you just create a coroutine 00:07:46.120 --> 00:07:47.320 and don't do anything with it, 00:07:47.360 --> 00:07:49.080 it probably still won't catch it, just to be clear. 00:07:49.580 --> 00:07:50.540 Anyway, so here's how it works. 00:07:50.800 --> 00:07:53.860 You can say, create a context manager 00:07:54.120 --> 00:07:55.360 with block and async with block, 00:07:55.460 --> 00:08:03.020 you say with no task links leaks and you run some code and here's a function call to create a task 00:08:03.200 --> 00:08:06.940 that is never awaited you wait long enough for that to come into existence and you're going to 00:08:06.950 --> 00:08:12.880 get an error right or this also works for threads just create a thread and never wait for it to stop 00:08:13.140 --> 00:08:18.240 so the context here is within this block of code i might be starting threads but they should all be 00:08:18.360 --> 00:08:23.839 done by the time we leave you know so this is pretty interesting and then another one is that's 00:08:23.860 --> 00:08:30.680 common is you can do things that have async counterparts, but the older way to do them 00:08:30.720 --> 00:08:32.140 would block the asyncio thread. 00:08:32.740 --> 00:08:37.080 And that's really bad because you want to spend as little time blocking that as possible 00:08:37.400 --> 00:08:39.800 because there's only one thread that does all the async work. 00:08:40.140 --> 00:08:44.219 So if you're doing FastAPI or whatever, one thread, don't block it, depending on how you 00:08:44.320 --> 00:08:45.220 set up your server, but generally. 00:08:45.760 --> 00:08:51.799 So if you had old code that said like time.sleep and then you convert that to async, this should 00:08:51.820 --> 00:08:58.760 be an await async io.sleep so that the it just lets the loop go for half a second rather than 00:08:58.960 --> 00:09:03.860 block the entire program so you can say with no event loop blocking right so those are the three 00:09:03.980 --> 00:09:08.040 types of tests so you can do it with context managers which is pretty cool you can also do it 00:09:08.080 --> 00:09:14.520 with decorators put them on a function no thread leaks no task leaks and so on and yeah you get 00:09:14.700 --> 00:09:20.120 errors like leaked task 2 or whatever right pretty descriptive shows you where it's called and so on 00:09:20.200 --> 00:09:22.040 Another one, though, you'll probably like this, Brian. 00:09:22.420 --> 00:09:23.480 A bunch of examples. 00:09:25.119 --> 00:09:26.460 But where are you? 00:09:26.980 --> 00:09:30.600 They also have a pytest plugin for it. 00:09:30.920 --> 00:09:34.860 So you can come and say pytest mark async.io 00:09:35.360 --> 00:09:38.020 and then run with no event loop blocking in there, 00:09:38.360 --> 00:09:39.280 which is pretty nice. 00:09:40.220 --> 00:09:41.880 It's maybe not exactly what I was looking for, is it? 00:09:42.120 --> 00:09:42.440 There we go. 00:09:42.480 --> 00:09:43.300 No, the pytest plugin. 00:09:43.840 --> 00:09:46.260 So then you can set it up as a marker with no leaks 00:09:46.620 --> 00:09:47.280 and things like that. 00:09:47.440 --> 00:09:47.640 Cool. 00:09:48.020 --> 00:09:48.140 Yeah. 00:09:48.440 --> 00:09:48.500 Yeah. 00:09:48.820 --> 00:09:49.220 No leaks. 00:09:49.240 --> 00:09:52.180 Anyway, yeah, if you're doing anything with async programming, 00:09:52.600 --> 00:09:55.240 might be worth throwing this on just to see what's going on. 00:09:55.660 --> 00:09:57.320 I don't think I would leave this on all the time. 00:09:57.510 --> 00:09:59.620 But having the unit test for it, good. 00:10:00.100 --> 00:10:02.260 And maybe if you're doing conversions, like I said, 00:10:02.380 --> 00:10:05.960 it's especially error prone to go from converting synchronous code to asynchronous code 00:10:06.280 --> 00:10:09.140 because it's so easy to overlook converting one bit here or there. 00:10:09.230 --> 00:10:10.720 So this would ideally catch it. 00:10:11.240 --> 00:10:11.860 Yeah, I'm not sure. 00:10:12.240 --> 00:10:15.060 It'd be one of those things of like also timing it. 00:10:16.920 --> 00:10:23.080 during development if you had this on to make sure things are like cool in your synchronous part or 00:10:23.280 --> 00:10:29.540 async part um and then you know how much slower is it or how much faster is it if you take that out 00:10:29.920 --> 00:10:35.900 if there's not much of a difference um yeah maybe leave it yeah yeah yeah exactly exactly but well 00:10:36.990 --> 00:10:43.800 yeah more django yeah i've actually been thinking about django a lot lately so i've got a a few 00:10:43.820 --> 00:10:48.800 articles. I just want to kind of run through a few of them that I ran across. I don't have much to 00:10:48.900 --> 00:10:53.480 say about either one of them, so I thought I'd combine them into one topic. So first off, we have 00:10:53.660 --> 00:11:00.100 from Paul Taylor, migrating from Celery to Django Tasks. And I know Django Tasks, I can't remember 00:11:00.160 --> 00:11:06.060 if it was just in this recent release. I think so. But they're a newish thing. So you might have 00:11:06.120 --> 00:11:11.400 some code around that you're a project that's using Celery already, and you want to use Django 00:11:11.460 --> 00:11:18.120 tasks instead so um walking through some of the some of the differences um and uh and and what to 00:11:18.190 --> 00:11:23.360 watch out for the different settings um and i did it made me want to play with it a little bit because 00:11:23.570 --> 00:11:29.540 um apparently django tasks has uh well if you combine it with cron task you can have tasks run 00:11:29.900 --> 00:11:35.440 with at certain intervals which is kind of fun that's neat you probably can do that with celery 00:11:35.490 --> 00:11:41.380 too but yeah but how many servers do you want this is like if your web app is running this 00:11:41.380 --> 00:11:43.520 happening versus are the servers talking to each other? 00:11:45.980 --> 00:11:50.080 Then next article, this is from Julia Evans, 00:11:50.460 --> 00:11:54.360 and she brought us all those cool zines 00:11:54.660 --> 00:11:57.540 about programming in GitHub and all that stuff. 00:11:58.140 --> 00:12:01.140 She wrote some notes on starting to use Django. 00:12:01.880 --> 00:12:04.380 One of the things I just like about this is she's 00:12:04.580 --> 00:12:05.880 experienced developers, 00:12:06.700 --> 00:12:09.160 you probably are already familiar with Julia Evans. 00:12:09.640 --> 00:12:13.840 But one of her comments about Django is it's less magic than Rails. 00:12:14.820 --> 00:12:18.480 And one of the things about that isn't just a style thing. 00:12:18.880 --> 00:12:26.040 It's when you leave a project and come back a few months later, can you find, can you pick it up and understand where things are? 00:12:26.220 --> 00:12:29.920 And just her commentary is just Django makes it more obvious. 00:12:30.520 --> 00:12:34.880 If you want to look for your views, they're in views.py, things like that. 00:12:35.960 --> 00:12:37.700 The built-in admin, of course, is nice. 00:12:38.140 --> 00:12:41.040 And the ORM, everybody loves the ORM. 00:12:41.260 --> 00:12:44.060 Or if you like the ORM, you love it, probably. 00:12:46.819 --> 00:12:52.920 Automatic migrations, that's a really cool built-in thing of Django. 00:12:53.300 --> 00:12:53.900 Good docs. 00:12:55.120 --> 00:12:57.400 And this is like the third one. 00:12:57.430 --> 00:12:59.020 Oh, built-in email was as neat. 00:12:59.100 --> 00:13:02.780 I haven't tried to use email with Django, but it's on my to-do list. 00:13:03.080 --> 00:13:04.080 Apparently, it's not that difficult. 00:13:04.950 --> 00:13:05.700 So that's cool. 00:13:07.280 --> 00:13:14.560 one of the things is that she's said that she's been using SQLite for Django in production and 00:13:14.900 --> 00:13:20.600 followed these instructions. And these instructions is the last article I want to talk about, which is 00:13:21.440 --> 00:13:28.400 the definitive guide to using Django with SQLite in production. And I just skimmed this, but 00:13:28.960 --> 00:13:35.600 it goes through how to set up databases and cache and all that stuff. I'm going to drop down to the 00:13:35.460 --> 00:13:41.600 conclusion there's quite a bit here and but the conclusion says um that is reduced complexity 00:13:42.200 --> 00:13:48.020 um it still looks kind of complex to convert to me but um but maybe it's less complex than 00:13:48.240 --> 00:13:55.000 keeping a sqlite or a postgres database around or something so yeah maybe backup is copy the file 00:13:55.540 --> 00:14:00.620 that's nice yeah so um anyway um and i can't remember which article was in there was a 00:14:00.580 --> 00:14:09.640 discussion around having in one of these Django articles about having tasks be stored in the 00:14:09.800 --> 00:14:16.040 database itself, which is interesting. I didn't know you could do that. So yeah, fun with Django. 00:14:16.280 --> 00:14:20.620 Yeah, very cool. I mean, in a sense, we're using SQLite in production. Python Bytes has a bunch of 00:14:20.980 --> 00:14:30.540 caching through disk cache, and disk cache is really just a fancy front end to SQLite. So 00:14:30.560 --> 00:14:38.420 So I want to talk about Datastar. So Datastar is a cool framework. This is not quite the exact right 00:14:39.570 --> 00:14:44.620 mental model for thinking about it, but it's kind of the spiritual successor to HTMX, I think. 00:14:45.020 --> 00:14:52.720 So the folks behind Datastar, they came from being contributors to the HTMX side and being 00:14:53.090 --> 00:14:56.720 big fans of it. So for those of you who don't know, HTMX, super cool library, 00:14:57.500 --> 00:15:01.320 it kind of extends the HTML markup to do more things. 00:15:01.640 --> 00:15:04.060 So instead of just saying, here's a button, 00:15:04.450 --> 00:15:05.600 you could say, here's a button, 00:15:06.120 --> 00:15:08.800 and on click, I want you to call this thing on the server. 00:15:09.120 --> 00:15:12.120 And when it comes back, I want you to replace this part of the page 00:15:12.130 --> 00:15:13.900 with what came back from the server and so on. 00:15:14.280 --> 00:15:21.140 And HTMX is great, but HTMX only does that sort of local server communication, right? 00:15:21.520 --> 00:15:22.800 So it might update some section, 00:15:22.930 --> 00:15:25.880 but what if when that part updates, another part of the page updates? 00:15:26.899 --> 00:15:28.800 and it gets a little bit more complicated. 00:15:29.280 --> 00:15:34.200 So what people have done is they paired HTMX with AlpineJS and other things, 00:15:34.440 --> 00:15:38.320 but AlpineJS has its sort of truth for what the data is, 00:15:38.320 --> 00:15:40.820 and then HTMX has the DOM and the server, 00:15:40.960 --> 00:15:44.760 and it's a little bit your job to juggle the go-between for these libraries, 00:15:44.940 --> 00:15:45.560 which is not ideal. 00:15:45.860 --> 00:15:47.540 So Datastar takes this idea and says, 00:15:47.720 --> 00:15:49.860 what if the server was the source of truth? 00:15:50.300 --> 00:15:53.920 What if we could have multiple parts of the page update 00:15:54.260 --> 00:15:56.100 in kind of a HTMX way. 00:15:56.190 --> 00:15:57.820 You say like, if you interact with this, 00:15:58.060 --> 00:15:59.000 you know, like click on this element, 00:15:59.090 --> 00:16:00.500 I want you to get this stuff from the server. 00:16:00.810 --> 00:16:02.020 And it sends back the page. 00:16:02.100 --> 00:16:03.720 And very much like PyView, 00:16:03.900 --> 00:16:04.980 which we talked about previously, 00:16:05.700 --> 00:16:08.500 it will take what comes back from the server, 00:16:08.960 --> 00:16:09.680 diff it and figure out, 00:16:09.690 --> 00:16:11.740 well, this section with this ID 00:16:11.770 --> 00:16:12.840 is going to be updated over here. 00:16:12.960 --> 00:16:14.900 And some other part is going to be updated with this 00:16:15.020 --> 00:16:16.020 because that ID part 00:16:16.290 --> 00:16:18.060 in the thing that came back matches over there. 00:16:18.460 --> 00:16:20.040 And it's got this really nice way 00:16:20.070 --> 00:16:21.640 to sort of be a little more holistic, 00:16:21.640 --> 00:16:27.100 but still do HTMX-like attributes with server-sent event things going on. 00:16:27.340 --> 00:16:28.900 So in a way, it's like PyView. 00:16:29.260 --> 00:16:31.440 But what's really different about this, two things. 00:16:31.840 --> 00:16:33.320 First is it's not a web framework. 00:16:33.340 --> 00:16:35.020 Like PyView is a web framework. 00:16:35.140 --> 00:16:36.200 Like Django is a web framework. 00:16:36.320 --> 00:16:37.860 Like Flask is a web framework. 00:16:38.180 --> 00:16:42.280 This is purely a JavaScript library that talks to the server 00:16:42.700 --> 00:16:44.680 and basically handles everything on the front end. 00:16:44.820 --> 00:16:46.440 It's only 11K too, by the way. 00:16:46.440 --> 00:16:47.360 So it's incredibly small. 00:16:47.680 --> 00:16:49.360 And it does what AlpineJS does. 00:16:49.860 --> 00:16:51.520 It has sort of a data binding thing. 00:16:51.800 --> 00:16:53.540 and the server can say, 00:16:53.800 --> 00:16:56.280 I know you have a variable called username. 00:16:56.820 --> 00:16:58.280 And if I update username on the server, 00:16:58.420 --> 00:17:00.460 it will automatically change the page 00:17:00.660 --> 00:17:02.080 everywhere username is used. 00:17:02.140 --> 00:17:03.980 So it has these things called signals as well. 00:17:05.060 --> 00:17:06.860 Pretty neat library, like this star field here. 00:17:06.939 --> 00:17:08.579 See how if you go to the website, 00:17:09.060 --> 00:17:10.300 it's following my mouse around. 00:17:10.620 --> 00:17:12.160 You can make it go faster or slower. 00:17:12.560 --> 00:17:14.079 It feels like you're in Star Wars, 00:17:14.540 --> 00:17:15.160 which is pretty cool. 00:17:15.220 --> 00:17:16.600 But all of that is being driven 00:17:17.519 --> 00:17:19.439 by server set events off of the server, 00:17:19.939 --> 00:17:20.760 which is pretty neat. 00:17:20.800 --> 00:17:22.160 There's a bunch of cool examples. 00:17:22.310 --> 00:17:25.100 So you can go to the examples page if I zoom back a bit. 00:17:26.020 --> 00:17:27.500 They also have this really fun video. 00:17:27.829 --> 00:17:29.160 So you should definitely watch the video. 00:17:29.980 --> 00:17:31.300 But let me show you an example. 00:17:31.480 --> 00:17:33.300 So there's a bunch of these examples. 00:17:34.100 --> 00:17:37.740 And if I open up two of these and put them side by side, 00:17:37.790 --> 00:17:41.200 I can use the new Vivaldi thing or I can tile them together. 00:17:41.620 --> 00:17:44.240 And if I get them to zoom the same size. 00:17:44.920 --> 00:17:47.260 So if you come over here, you can just type in. 00:17:47.740 --> 00:17:50.420 If you put these two side by side, you can say record. 00:17:50.780 --> 00:17:55.280 podcast and boom they're both going i don't know this one is going to finish that one i'm going to 00:17:55.390 --> 00:18:00.240 finish that let's uh show only the completed ones oh wow and that's cool it happens to be on my 00:18:00.710 --> 00:18:05.100 same machine but really they could be anywhere there's a really bunch of a bunch of interesting 00:18:05.360 --> 00:18:11.880 performance things around with data star so you kind of like htmx be like ah but it's a little 00:18:12.000 --> 00:18:17.480 bit not quite enough for what i need to do check this out it's a really cool thing and this episode 00:18:17.600 --> 00:18:20.780 with the Datastar team is coming out on Talk Python this week. 00:18:20.810 --> 00:18:24.380 I wanted to feature Datastar on the show sooner, 00:18:24.790 --> 00:18:27.060 but then when I knew I was going to have them on Talk Python, 00:18:27.110 --> 00:18:29.720 I was like, let me just wait until I get that episode recorded. 00:18:29.920 --> 00:18:32.380 People who are more interested can listen to that as well. 00:18:32.940 --> 00:18:33.920 So that's coming out. 00:18:34.540 --> 00:18:37.820 Plus a couple bonuses on this, 00:18:38.550 --> 00:18:40.580 that it won the website, 00:18:40.840 --> 00:18:42.720 just the retro look of it looks awesome. 00:18:43.120 --> 00:18:43.860 It's great, isn't it? 00:18:44.320 --> 00:18:47.960 And that they use the term hypermedia. 00:18:48.400 --> 00:18:51.620 Kind of love that back to the origins. 00:18:52.500 --> 00:18:53.240 Yeah, yeah, for sure. 00:18:53.820 --> 00:18:57.940 And there's also this really nice article by Chris May, 00:18:58.270 --> 00:19:00.440 who is a very big fan of HTMX, 00:19:00.490 --> 00:19:04.160 gave some Django FlaskCon talk on it, 00:19:05.000 --> 00:19:06.540 and basically went through and said, 00:19:06.600 --> 00:19:09.260 why do I think I'm using Datastar these days? 00:19:09.460 --> 00:19:13.460 So really nice example, but got some Python examples. 00:19:13.540 --> 00:19:16.140 There's a Python SDK that you can bring in. 00:19:16.540 --> 00:19:19.120 So if you were using Flask, use the SDK. 00:19:19.260 --> 00:19:21.520 If you're using FastAPI, use the SDK or whatever. 00:19:21.760 --> 00:19:22.820 But yeah, super neat. 00:19:23.400 --> 00:19:24.060 Okay, cool. 00:19:24.840 --> 00:19:25.200 All right. 00:19:25.540 --> 00:19:26.980 That's it for all of our topics, isn't it? 00:19:27.440 --> 00:19:27.660 Yeah. 00:19:28.960 --> 00:19:30.380 Got anything out there you want to cover? 00:19:30.560 --> 00:19:30.940 Any extras? 00:19:32.200 --> 00:19:32.380 Okay. 00:19:32.560 --> 00:19:34.700 So yeah, a couple of extras. 00:19:35.000 --> 00:19:35.320 Let's see. 00:19:35.560 --> 00:19:36.580 I'm all zoomed out. 00:19:36.700 --> 00:19:41.340 So I did bring up Django chat before I, the, the, 00:19:41.700 --> 00:19:44.760 I was lucky enough to be asked to be on the show as well. 00:19:44.960 --> 00:19:48.840 So I was talking about lean TDD and a lot of other stuff on the, 00:19:49.210 --> 00:19:52.460 the Django chat podcast. I, you know, 00:19:52.540 --> 00:19:56.400 one of the things they asked me is, is the, is about the, what, 00:19:56.540 --> 00:20:00.520 the trends in web frameworks for Python. And I'm like, man, 00:20:00.640 --> 00:20:03.420 I'm the wrong guy to ask about that. Yeah, sure. Okay. 00:20:04.980 --> 00:20:08.380 You mean the ones that run on the hardware that control the Wi-Fi signals? 00:20:08.960 --> 00:20:09.180 Yeah. 00:20:10.560 --> 00:20:13.640 Anyway, so I am working a little bit at Django lately, 00:20:14.179 --> 00:20:16.680 but I'm by no means a Django expert. 00:20:17.310 --> 00:20:23.660 But we did get into the Lean TDD and inverting the testing pyramid a little bit. 00:20:23.850 --> 00:20:27.000 One of the things I love about this and was really fun because Carlton, 00:20:27.210 --> 00:20:33.480 when I brought up the fact, brought up some reasons to shy away from unit tests as much. 00:20:34.240 --> 00:20:37.120 Carlton kind of got his feathers ruffled, 00:20:37.210 --> 00:20:41.940 and we walked through some of the good aspects of unit tests 00:20:42.200 --> 00:20:44.740 and where you might want to keep them, where you might want to ditch them. 00:20:44.960 --> 00:20:46.120 So that was fun. 00:20:47.280 --> 00:20:53.980 The next extra is that I did notice that the PEP 686, 00:20:54.380 --> 00:20:58.740 making UTF-8 mode the default, is now, or maybe it was. 00:20:59.440 --> 00:21:00.720 Maybe it was a while ago. 00:21:01.140 --> 00:21:03.160 But anyway, I just noticed that it was finals. 00:21:03.660 --> 00:21:06.800 If we haven't covered it already, it's finalized in 3.15. 00:21:07.120 --> 00:21:07.560 It'll be there. 00:21:07.760 --> 00:21:08.420 So that's good. 00:21:09.260 --> 00:21:10.060 I think that's interesting. 00:21:10.240 --> 00:21:14.220 This is a really old request, but it didn't get until next year, right? 00:21:14.360 --> 00:21:15.120 3.15. 00:21:15.480 --> 00:21:17.760 So this was originally started in 2022. 00:21:18.440 --> 00:21:18.780 Yeah. 00:21:19.300 --> 00:21:22.300 But it's not yet in Python, right? 00:21:22.380 --> 00:21:24.140 It's 3.15, as you point out. 00:21:25.640 --> 00:21:28.400 Yeah, I'm looking forward to having the default be just UTF-8. 00:21:29.040 --> 00:21:30.480 Yeah, I mean, if you're going to have a default. 00:21:32.740 --> 00:21:37.540 Let's pick the one that is mostly used and supports all the different languages and emojis. 00:21:38.120 --> 00:21:39.180 It's important to have emojis. 00:21:39.530 --> 00:21:39.720 Yeah. 00:21:40.740 --> 00:21:46.260 Before we move on, I do have, I guess, a way side tangent topic. 00:21:47.370 --> 00:21:54.380 Kind of the sci-fi-ness of Datastar reminded me that recently I remembered the cheesy 80s movie 00:21:54.470 --> 00:21:58.140 that reminded me of Tesla's Cybertrucks. 00:21:58.580 --> 00:22:01.500 And the cheesy movie was called Megaforce. 00:22:01.680 --> 00:22:02.400 And it's from 81. 00:22:02.760 --> 00:22:03.960 did you ever see Megaforce? 00:22:04.180 --> 00:22:06.380 I have somehow missed this cultural phenomenon. 00:22:06.660 --> 00:22:08.580 Well, you're probably well off 00:22:08.800 --> 00:22:11.720 because Rotten Tomatoes gives it a 6%. 00:22:13.580 --> 00:22:15.480 And the reason why I think about it 00:22:15.560 --> 00:22:17.720 when I see Teslas is because of these trucks. 00:22:17.940 --> 00:22:20.700 So these tanks in there, in the Megaforce, 00:22:20.860 --> 00:22:22.460 kind of remind me of, well, 00:22:22.840 --> 00:22:24.320 just sort of the angles and stuff 00:22:24.460 --> 00:22:25.380 kind of remind me of Cyber. 00:22:25.520 --> 00:22:26.580 They do have that, don't they? 00:22:27.520 --> 00:22:27.920 Incredible. 00:22:28.360 --> 00:22:29.120