Update 487-building-rust-extensions-for-python.txt

transcripts/487-building-rust-extensions-for-python.txt

@@ -734,7 +734,7 @@
 
 00:24:21 Another example is Jitter, which I showed you.
 
-00:24:24 We released Jitter a year ago now.
+00:24:24 We released Jiter a year ago now.
 
 00:24:27 It is the most downloaded JSON parser in Python other than the one in the standard library.
 
@@ -818,7 +818,7 @@
 
 00:27:26 We don't really think about compiling much in Python.
 
-00:27:28 We don't think about it, but you can think of import time when you do different stuff or you think about static typing when you go and run PyWright  over your code.
+00:27:28 We don't think about it, but you can think of import time when you do different stuff or you think about static typing when you go and run Pyrite over your code.
 
 00:27:37 And that is very similar in some ways to compile time.
 
@@ -842,7 +842,7 @@
 
 00:28:25 If you were using most other, if you were using cargo, you would have to take care.
 
-00:28:30 I mean, putting the controversy over Surdi to one side for a minute, you would have to take care of compiling that code yourself every time you wanted to go and go and use it.
+00:28:30 I mean, putting the controversy over Serde to one side for a minute, you would have to take care of compiling that code yourself every time you wanted to go and go and use it.
 
 00:28:38 Whereas Action PyPI does an amazing job of distributing compiled Rust for virtually every ecosystem, every architecture, and it just working when you install it.
 
@@ -1070,6 +1070,8 @@
 
 00:36:14 Does that mean, in theory, if you've got this, that you could use this within, for example, CI to only run unit tests, systems that have changed or direct descendants of that package?
 
+00:36:27 We do that.
+
 00:36:25 Because I presume we do do that because we've got a lot of money on CI.
 
 00:36:30 And so we've had to invest a lot of money to like figure out how do we narrow down the tests.
@@ -1084,7 +1086,9 @@
 
 00:36:43 It's a little bit like what you did, Samuel, with Pydantic and Pydantic Core.
 
-00:36:47 So import linter is pure Python, but it has a dependency, which is Grimp, which is, I mean, it's got Python and Rust in at the moment.
+00:36:47 So Import-Linter is pure Python.
+
+00:36:49 Yeah.
 
 00:36:55 But that is just a Python API for building a graph.
 
@@ -1280,7 +1284,7 @@
 
 00:43:32 I don't know how long ago that was you, you were trying, but I think it's, yeah, reduced significantly.
 
-00:43:37 So, I mean, I did this quite a lot of the same work in Pydantic Core to avoid the overhead of calling into and out of it lots of times.
+00:43:37 So, I mean, I did quite a lot of the same work in Pydantic Core to avoid the overhead of calling into and out of it lots of times.
 
 00:43:43 And I think that's less of a thing now than it used to be.
 
@@ -1310,7 +1314,7 @@
 
 00:44:46 I don't know if that's in here as well.
 
-00:44:48 I maintain watch files, which is the file watching library used by UV-con and some other things.
+00:44:48 I maintain watch files, which is the file watching library used by UVcorn and some other things.
 
 00:44:55 And that is, again, wrapping a Rust library for getting fast system notifications.
 
@@ -1858,4 +1862,6 @@
 
 01:02:00 Now get out there and write some Python code.
 
+01:02:02 Thank you.
+
 01:02:02 I'll see you next time.