Brian Okken: Hello and welcome to Python Bytes, where we deliver Python news and headlines directly to earbuds.
Brian Okken: This is episode 461, recorded December 9th, 2025.
Brian Okken: And I am Brian Okken.
Brian Okken: And I am Michael Kennedy.
Brian Okken: And this episode is sponsored by yours truly and Michael.
Brian Okken: So both of us Talk Python Training.
Brian Okken: Always some great stuff.
Brian Okken: I just finished the AI, the recent AI agent course.
Brian Okken: Oh, you did?
Brian Okken: great yeah thank you yeah awesome really enjoyed it uh some great content there and um so but
Brian Okken: there's plenty of other stuff to do there's even a py test course there but if you'd like a really
Brian Okken: complete py test course head on over to python test.com we have uh there's the complete course
Brian Okken: there uh thanks to patreon supporters also there's um a new book out from michael and uh and a book
Brian Okken: that i'm working on so lots of ways you can support us and if you don't if you just want to support us
Brian Okken: by sending us topics.
Brian Okken: We'd like that too.
Brian Okken: You can connect with us.
Brian Okken: There's a contact form on the website
Brian Okken: on pythonbytes.fm
Brian Okken: or you can reach us on Bluesky or Mastodon.
Brian Okken: And if you'd like to, if you're listening,
Brian Okken: we love you.
Brian Okken: But we also would like you to check out
Brian Okken: our video stuff every once in a while.
Brian Okken: Head on over to pythonbytes.fm/live
Brian Okken: and you can be part of the audience
Brian Okken: or just watch it afterwards.
Brian Okken: And finally, please subscribe to our newsletter
Brian Okken: or essentially it's occasionally we send out little news bits,
Brian Okken: but mostly it's the show notes from the show.
Brian Okken: So we send out, after we get it all done,
Brian Okken: we send out a newsletter that has all the links
Brian Okken: so you don't have to take notes while you're listening.
Brian Okken: Now for our first topic, Michael.
Michael Kennedy: Our first topic is going to be a tour of peps,
Michael Kennedy: a brand new PEP in a PEP that we spent a fair amount of time talking about.
Michael Kennedy: The first one is PEP 798, Unpacking in Comprehensions.
Michael Kennedy: So this one is a little bit funky.
Michael Kennedy: It's currently in draft stage targeting Python 3.15.
Michael Kennedy: It's pretty minor, but I think it brings some consistency to it.
Michael Kennedy: So I linked to the conversation here.
Michael Kennedy: And the idea is right now, if I have a function that
Michael Kennedy: takes an arbitrary number of positional keywords,
Michael Kennedy: you would say star args, right?
Michael Kennedy: Star args, star kwa args is like a pretty common theme
Michael Kennedy: So if I had something that said star args, and I wanted to push a tuple of values as those positional parameters, I would say star tuple in the function call.
Michael Kennedy: Kind of like you say star star for a dictionary to say keyword arguments, right?
Michael Kennedy: So the idea here is that that works for function calls, but it doesn't work for comprehensions, list comprehensions, set comprehensions, and so on, if you have an iterable.
Michael Kennedy: Right now what we have, and this is super confusing to me, I always get the order wrong,
Michael Kennedy: or at least I'm always uncertain of the order, is I can say, you know, basically X for X in Y,
Michael Kennedy: Y for Y in thing, if I've got a set of lists or intervals and I want to turn them into
Michael Kennedy: like one big list as a comprehension, you can basically do like a double comprehension
Michael Kennedy: in one thing. And I'm always like, which one is the collection and which one is the item,
Michael Kennedy: you know, so this kind of solves that.
Michael Kennedy: It says you can just say in the comprehension,
Michael Kennedy: you say star iterable for iterable in some list of iterables.
Michael Kennedy: And it makes it real simple, right?
Michael Kennedy: So you can do that for, pulled up official pep.
Michael Kennedy: You can do it for list comprehensions, set comprehensions,
Michael Kennedy: dictionary comprehensions.
Michael Kennedy: If you have a list, if you have an iterable of dictionaries,
Michael Kennedy: you can create a dictionary comprehension.
Michael Kennedy: And you can do it for generators.
Michael Kennedy: if your generator generates iterables.
Michael Kennedy: Does that make sense?
Brian Okken: Yeah.
Michael Kennedy: So that's pretty much it.
Michael Kennedy: What do you think?
Brian Okken: That's cool.
Brian Okken: So that's not something you do now?
Brian Okken: This is a proposal?
Brian Okken: Is that right?
Michael Kennedy: Yes, this is a draft for 3.15.
Michael Kennedy: Okay.
Michael Kennedy: And just shout out for a little bit of credit.
Michael Kennedy: This is Adam Hartz and Eric Demain
Michael Kennedy: for the people proposing it.
Michael Kennedy: And the sponsor is Yelda Zilastra.
Michael Kennedy: Sorry, if I messed that up,
Michael Kennedy: I gave it my best shot, folks.
Michael Kennedy: So anyway, that's my main topic here for this first one
Michael Kennedy: is this unpacking in comprehensions.
Michael Kennedy: We've had unpacking in other places, into variables.
Michael Kennedy: We've had unpacking into function calls.
Michael Kennedy: We have not had them in comprehensions.
Michael Kennedy: And they've honestly, this double comprehension,
Michael Kennedy: like double layered comprehension thing
Michael Kennedy: has always been complicated.
Michael Kennedy: And so I'm here for it.
Michael Kennedy: I mean, it does add another thing to language
Michael Kennedy: and everything you add to a language
Michael Kennedy: just makes it more complicated.
Michael Kennedy: But in this case, I think it's well worth it.
Michael Kennedy: Now, go ahead.
Brian Okken: Oh, I just wanted to say, speaking of the unpacking, use the star or asterisk, but one of my favorite names for that character is splat.
Brian Okken: Splat.
Michael Kennedy: Let's call them splatted comprehensions.
Michael Kennedy: Here, hold on.
Michael Kennedy: I'll just edit this and we'll fix this real quick.
Michael Kennedy: I'm going to change the, you know what, my screen is too small.
Michael Kennedy: I was going to edit the text, right?
Michael Kennedy: Okay, so that's all good.
Michael Kennedy: Now the next one is just a really quick follow-up on a PEP as well.
Michael Kennedy: Before we move off of Focus on Me.
Michael Kennedy: Remember how excited you were and I was about explicit lazy imports?
Michael Kennedy: As in lazy...
Michael Kennedy: Are they going to take it out?
Michael Kennedy: No.
Michael Kennedy: Dear Pep 810 authors, Barry Warsaw writes,
Michael Kennedy: this steering council is happy, happy to unanimously accept Pep 810 explicit lazy imports.
Michael Kennedy: Congratulations.
Michael Kennedy: You now have a job to implement.
Michael Kennedy: And it's, yeah.
Michael Kennedy: The same is true for all the other alternative keywords
Michael Kennedy: we come up with.
Michael Kennedy: So lazy it is.
Michael Kennedy: I know.
Michael Kennedy: That's anyway, a little bit of background
Michael Kennedy: on some of the thinking the steering council put out there.
Michael Kennedy: But yeah, unanimously and happy.
Brian Okken: Yay.
Michael Kennedy: Good.
Michael Kennedy: Yeah, that's pretty good.
Michael Kennedy: So happy to see that.
Michael Kennedy: And by the way, just a little shout out
Michael Kennedy: for the live stream folks.
Michael Kennedy: I'm going to have Barry Warsaw and a bunch of other folks
Michael Kennedy: on to do a year in review three hours,
Michael Kennedy: two hours and 40 minutes from now on Talk Python.
Michael Kennedy: So that's going to be fun.
Michael Kennedy: We'll hear from Barry over there, but probably not about the path.
Michael Kennedy: All right, over to you, Brian.
Brian Okken: What am I talking about?
Brian Okken: I'm going to talk about another new release or an upcoming release, Pandas 3.0.
Brian Okken: So the Pandas 3.0.0, so 3.0.0.
Brian Okken: There's a release candidate zero that's been out since sometime last week.
Brian Okken: And then apparently there's going to be an official 3.0 released in a few weeks.
Brian Okken: but that was a week ago so maybe a couple weeks from now not sure um so what do we got in here
Brian Okken: i'm pretty excited about this actually uh we've got um what's new there's a there's a dedicated
Brian Okken: string data type by default and this is just kind of great so if uh normally in things that with
Brian Okken: strings in them they would show up as objects but clearly they're strings so there's a new string
Brian Okken: type um and it does change things a bit um if you have any the any missing things it'll be an uh
Brian Okken: N-A-N, sentinel, to say that there's nothing there.
Brian Okken: What's great about this is once you have this str type, D type,
Brian Okken: or str D type, you can only put strings or nans in it.
Brian Okken: There's nothing else allowed.
Brian Okken: So nothing weird shows up.
Brian Okken: It's not just a generic object.
Brian Okken: There's a lot of other implications around this.
Brian Okken: The str can only hold strings in the sentinel, of course.
Brian Okken: The missing values are sentinel inferred by default for string data.
Brian Okken: Anyway, check out the PEP 14 to get a little more information.
Brian Okken: There will, there's other implications around this, but I think it's a really good thing.
Brian Okken: Copy on write also is kind of a really exciting thing that hopefully nobody will really notice.
Brian Okken: But the idea is really anything that results in an indexing operation will return essentially a copy of things.
Brian Okken: So you don't, there's not, or not, not a copy.
Brian Okken: It'll be a reference.
Brian Okken: It's, and it only, only makes a copy of actually modify something.
Brian Okken: So, so pandas will keep track of whether or not you've changed it.
Brian Okken: And if you haven't changed it, it's just a copy of the data there.
Brian Okken: This will say, this should save a lot of time and space.
Michael Kennedy: So I think that's going to save a ton of, especially memory.
Michael Kennedy: Because if I remember correctly, I'm not a pandas expert by any stretch of the imagination.
Michael Kennedy: But when you call operations like filter operations or other transform operations, it doesn't in place modify it.
Michael Kennedy: It returns a new data frame.
Michael Kennedy: Like if I add a column to a data frame with the operation, I get an entire copy of that data frame plus the column.
Michael Kennedy: You know, one of the new column.
Michael Kennedy: If you've got five million rows loaded and you call those five or ten times, like you're all of a sudden, it's piling up fast.
Brian Okken: Yeah.
Brian Okken: And it says the main goal is to change the user API to be more consistent and predictable.
Brian Okken: And I think this is right because, I mean, we're doing like matrix operations and stuff,
Brian Okken: and we'd really like it to be kind of like math where you don't really care about the
Brian Okken: size or timing implications.
Brian Okken: You're just, this is what I want to do.
Brian Okken: And having that be more consistent and hidden behind the scenes, I think it's going to be
Brian Okken: great.
Brian Okken: It's going to make this a lot easier to learn.
Brian Okken: They're cleaning up a lot of the API and stuff.
Brian Okken: It's really cool.
Brian Okken: We had covered this in one of the other episodes that was coming.
Brian Okken: PD call syntax can now be used in data frame assign and location.
Brian Okken: And this idea is that basically you could just say,
Brian Okken: I want to assign a new column with the addition of like two other columns or something,
Brian Okken: or some operation.
Brian Okken: And it just does it right there.
Brian Okken: Like instead of having to do a lambda expression inside,
Brian Okken: you can just do the expression.
Brian Okken: It's really kind of a great syntax.
Brian Okken: We've got a copy of the syntax in the show notes, but that's pretty great.
Brian Okken: Some changes to deprecation policy, probably because of some of these changes that they're doing a three-stage deprecation thing.
Brian Okken: But I think this is good.
Brian Okken: I think that basically open source projects are being used more.
Brian Okken: The ones that they have to think about this, how to keep track, keep it fun to maintain, but also moving with the times.
Brian Okken: And I think these are good calls.
Brian Okken: A bunch of other enhancements as well, so check those out.
Brian Okken: But I think this is a really good direction.
Brian Okken: and I can't wait to see 3.0 pandas come out.
Brian Okken: This will be great.
Michael Kennedy: Yeah, that's pretty exciting.
Michael Kennedy: That's a pretty major change.
Michael Kennedy: All right.
Michael Kennedy: What's up next?
Michael Kennedy: This episode has typos in it, Brian.
Michael Kennedy: Oh, no.
Michael Kennedy: I'll try to fix it.
Michael Kennedy: I know.
Michael Kennedy: Well, remember I spoke about code spell,
Michael Kennedy: all one word, code spell,
Michael Kennedy: and it was a misspelling finder,
Michael Kennedy: not a spell checker, right?
Michael Kennedy: The spell checker looks for words
Michael Kennedy: that it knows are good and says,
Michael Kennedy: I don't know that word.
Michael Kennedy: That must be misspelled.
Michael Kennedy: In programming, obviously, there's all these symbols and all sorts of stuff.
Michael Kennedy: One of the things that drives me crazy is when my editor suggests that a library that I'm importing is misspelled,
Michael Kennedy: but it's the library's name correctly.
Michael Kennedy: I'm like, hmm, well, I can't write it any other way.
Michael Kennedy: This is the only way it works.
Michael Kennedy: I'm sorry, spellchecker, but do I really got to go through and tell you that this is the name of the library I'm using?
Michael Kennedy: Yes, apparently I do.
Michael Kennedy: So this like code spell, this thing called typos, also looks for known misspellings like ADN for a common misspelling of and and so on.
Michael Kennedy: Super good.
Michael Kennedy: Why are we back?
Michael Kennedy: Well, Sky Cosco wrote and said, code spell is cool, but you should check out typos.
Michael Kennedy: So typos, I believe it is written in Rust.
Michael Kennedy: Yes, 99.9%.
Michael Kennedy: That's three nines Rust.
Michael Kennedy: Pretty good.
Michael Kennedy: And 0.0% Python, but it's still mentioned.
Michael Kennedy: So it must be less than one-tenth of 1%.
Michael Kennedy: But it's a little more full-featured for people that like this.
Michael Kennedy: So, for example, it has a GitHub action that you could just put into all of your PRs.
Michael Kennedy: That's kind of cool, if you want.
Michael Kennedy: It's like a gated thing for PRs and commits and so on.
Michael Kennedy: But the best thing about it, I guess two things.
Michael Kennedy: One is it uses the concrete syntax tree rather than actually just searching text.
Michael Kennedy: So what it can do is it can find partial bits of words that are misspelled.
Michael Kennedy: Maybe this is actually not related to that, but it does find partial misspellings.
Michael Kennedy: So for example, if you write connecton string instead of connection string with snake casing,
Michael Kennedy: whatever, it says, hey, guess what?
Michael Kennedy: The word connection and connection underscore string without the I is a misspell.
Michael Kennedy: Maybe you should change, you know, connecton to connection or connector or whatever.
Michael Kennedy: And it gives you a nice little UI for that.
Michael Kennedy: So that's one.
Michael Kennedy: I really like that.
Brian Okken: But like that's super cool that it can detect misspellings within, you know, snake case words.
Michael Kennedy: So, yeah, yeah, this is a it's a big improvement.
Michael Kennedy: And PyCharm does this as well, by the way, which is really nice.
Michael Kennedy: But I believe PyCharm is a built checker, not a misspelling finder or whatever.
Michael Kennedy: Pretty sure.
Michael Kennedy: Anyway, this is really nice that it does this.
Michael Kennedy: The other thing that's super cool, and this is why Sky wrote to us,
Michael Kennedy: is it actually has a VS Code in Friends extension in language server.
Michael Kennedy: So what you can do is basically install this as an extension in VS Code
Michael Kennedy: or Cursor or Google Antigravity or, you know, you name all the others, right?
Michael Kennedy: Because it's also in the OpenVSX registry.
Michael Kennedy: So you can install that there.
Michael Kennedy: And then just as you're writing code, you get little squigglies
Michael Kennedy: and you hit get alt enter actions to fix it.
Michael Kennedy: So you don't even have to run the client
Michael Kennedy: or the GitHub thing and so on,
Michael Kennedy: which the code spell has no editor integration.
Michael Kennedy: So it's really the fact that this is like that,
Michael Kennedy: a little better, runs in editors.
Brian Okken: That's cool.
Brian Okken: Yeah.
Brian Okken: Actually, I don't remember the last time
Brian Okken: I actually ran a spell checker independently.
Brian Okken: I just rely on those in-editor things.
Brian Okken: So do I.
Michael Kennedy: So do I.
Michael Kennedy: So yeah, it's also got LSB for other things, I guess.
Michael Kennedy: Yeah, that means you can even use it in NeoVim or Vim or Zed or whatever, right?
Michael Kennedy: So it's not just even the extensions.
Michael Kennedy: It's actually because the LSP even goes farther than that.
Michael Kennedy: Cool.
Michael Kennedy: Yeah.
Michael Kennedy: Anyway, thank you, Sky, for the follow-up and good suggestion.
Brian Okken: All right.
Brian Okken: Apparently, I'm missing having a testing podcast.
Brian Okken: So I've got two topics that I'd like to talk about, a couple of testing topics.
Brian Okken: First one came in.
Brian Okken: It's called Slowlify.
Brian Okken: It came in from Brian Skin.
Brian Okken: So thank you, Brian, for sending in this idea.
Brian Okken: So here's an interesting idea.
Brian Okken: So this is a project to simulate overloaded, slow, resource-constrained machines.
Brian Okken: So basically to make your tests flakier or something.
Brian Okken: Nice flaky tests.
Brian Okken: But the idea around it is a test is working fine locally,
Brian Okken: but you throw it up in CI and it fails for some reason.
Brian Okken: And it might be because you've got a CI image that is more constrained.
Brian Okken: So this allows you to do things like muck with how much memory is around
Brian Okken: and how many CPUs are available and stuff.
Brian Okken: It requires you to run it on a Linux machine with Cgroups V2 around
Brian Okken: because that's how it throttles the CPU and memory and stuff.
Brian Okken: But it shouldn't be hard to come by, hopefully.
Brian Okken: And yeah, then you can check to muck with things to find out,
Brian Okken: to try to simulate locally a failure that's happening in CI.
Brian Okken: So really nice there.
Brian Okken: The other topic I'd like to talk about testing-related is,
Brian Okken: this comes from Ned Batchelder.
Brian Okken: Actually, it's his article, Why Your Mock Breaks Later.
Brian Okken: And actually, I think it should be stronger than this.
Brian Okken: basically don't the don'ts and do's of uh mocking and the gist of it is uh overly aggressive
Brian Okken: mocks can can work fine at first but then break later recently a lot of people were doing uh
Brian Okken: all this pop down if you've like let's say you're reading a file and you want you want to pat you
Brian Okken: when the file gets opened you don't really actually want to file the muck with the file you
Brian Okken: want to be able to to mock that or patch it so one of the things that some people do is to patch the
Brian Okken: open function and one of the ways people do it is patching built-ins open this is not how you want
Brian Okken: to do it this is the don't do this version and uh let's just zoom in a bit don't do the built-ins
Brian Okken: open because it it like patches everything and it's causing problems in uh it was causing problems
Brian Okken: of coverage because coverage also wants to open something and you're basically patching open for
Brian Okken: everything in your app in your program including coverage when it's running on top of it so you
Brian Okken: don't want to do that you only want to patch where where you are so the proper way is wherever
Brian Okken: like if you're in a the example is you've got a user um file you want to patch right there in my
Brian Okken: product.user, the dot following of where it is.
Brian Okken: Exactly where it is.
Brian Okken: That's the gist of it is,
Brian Okken: don't mock the thing you're importing
Brian Okken: after you've imported it, mock it there.
Brian Okken: And it's a good lesson.
Brian Okken: I didn't think that this,
Brian Okken: I thought that was fairly widely known,
Brian Okken: so I didn't realize it was an issue.
Brian Okken: He went ahead and did a search for Python.
Brian Okken: In GitHub, you can search for built-ins open with tests in there and patches and stuff, either patches or whatever, monkey patching or patching or mock patching.
Brian Okken: Found 44,000 files that were doing the bad one within GitHub.
Brian Okken: So this is all naughty.
Michael Kennedy: I don't know what kind of GitHub badge you get for 44,000 PRs getting accepted, but Ned's got himself a real opportunity here to get a 100% sort of badge.
Brian Okken: I don't think he wants to fix them all, but yeah.
Michael Kennedy: No, that's an interesting way, an interesting metric.
Brian Okken: Yeah, and actually at the end of the article, also I'd like to point out, he talks about some mocking practices.
Brian Okken: Make sure you use autospec equals true to make sure that your mocks strictly behave like the original.
Brian Okken: I wholeheartedly agree with that.
Brian Okken: Make assertions about how your mock is called.
Brian Okken: Actually, the rest of this is stuff that I actually want to go check out
Brian Okken: because I do remember this functional core imperative shell talk
Brian Okken: and some of these other things, dependency injection.
Brian Okken: I'm not sure if I agree with all of Ned's stuff, but that's all right.
Brian Okken: Some other interesting things to read about with mocking.
Brian Okken: And I imagine he knows more than I do because I don't usually mock.
Brian Okken: I don't mock very much.
Brian Okken: It's not very nice to do, honestly.
Brian Okken: It's not very nice.
Michael Kennedy: So yeah, but sometimes it's necessary.
Brian Okken: And sometimes it's necessary.
Brian Okken: You know what is nice, though?
Brian Okken: Extras.
Brian Okken: Extras, yeah.
Brian Okken: Yeah, I do have extras.
Brian Okken: Should I go ahead and run through them?
Brian Okken: All right.
Brian Okken: So I've already got my stuff up.
Brian Okken: Let's go.
Brian Okken: This is a great, there was a great mini documentary of FastAPI,
Brian Okken: The Rise and Fall, Rise and Rise, not The Rise and Fall,
Brian Okken: The Rise and Rise of FastAPI with Sebastian Ramirez.
Brian Okken: And it's like an eight-minute video.
Brian Okken: It's a really fun video of him talking about it.
Brian Okken: He's such a genuine, nice dude also.
Brian Okken: Yeah, he really is.
Brian Okken: I am still writing, Lean TDD, the e-book in progress.
Brian Okken: You go to the table of content.
Brian Okken: Oh, I made a couple of changes.
Brian Okken: So somebody requested that not only do I,
Brian Okken: when I release a new chapter to release the full thing,
Brian Okken: but also the latest one.
Brian Okken: And that way people can just like just throw the latest one on their Kindle and just have one chapter where they can either replace the whole thing or if they've taken notes on other stuff to just do the updates, the new chapters.
Brian Okken: So I'm going to do that now or at least have started.
Brian Okken: We'll see. It's a little extra work, but that's all right.
Brian Okken: I got the building on lean done and it was long enough to talk about lean.
Brian Okken: I think that it made sense to split it.
Brian Okken: And I was going to do finding waste in test-driven development as part of that chapter, but I'm going to make it its own chapter now.
Brian Okken: So I'm going to do that.
Brian Okken: I wanted to do a sneak peek.
Brian Okken: Oh, never mind.
Brian Okken: Of the table of contents in progress so far.
Brian Okken: So I'm making some good progress.
Brian Okken: I've got an outline for where I'm going in the future.
Brian Okken: Where are we now?
Brian Okken: We're going to do finding waste in TDD next year.
Brian Okken: It's not going to be a huge book.
Brian Okken: Probably, I'm guessing.
Brian Okken: So right now we're up to, what, 30 pages?
Brian Okken: is a PDF.
Brian Okken: I'm guessing it will be under 100 pages when I'm done.
Brian Okken: So it's not a huge book, but it's also not expensive.
Brian Okken: It's $10.
Michael Kennedy: At least my experience is PDFs usually have more content per page than e-books,
Michael Kennedy: at least if you ask Amazon how many pages is it.
Brian Okken: Yeah, and even like way more.
Brian Okken: Yeah, it's more content per page for e-book, but also per print book.
Brian Okken: So print book isn't usually an 8.5 by 13 page.
Brian Okken: So yeah.
Brian Okken: Last one, my extra Python 3.14.2 was released December 5th.
Brian Okken: We haven't had 3.14 around for that long,
Brian Okken: but people are upgrading, which is great,
Brian Okken: and they're not afraid to upgrade,
Brian Okken: but they're finding a few things.
Brian Okken: So there were a handful of fixes.
Brian Okken: There were some exceptions in multiprocessing.
Brian Okken: I didn't notice those, but some people noticed them.
Brian Okken: Data classes without an NITs were throwing exceptions.
Brian Okken: Anyway, they fixed some critical things in 3.14,
Brian Okken: And I appreciate the core team being on top of it.
Michael Kennedy: So that's great.
Michael Kennedy: Yeah, awesome.
Michael Kennedy: That one flew under my radar somehow.
Michael Kennedy: I didn't notice it.
Michael Kennedy: So very exciting.
Michael Kennedy: Time to upgrade some stuff.
Brian Okken: All right.
Michael Kennedy: Do you have any extras?
Michael Kennedy: Well, I do.
Michael Kennedy: I have some repeat extras in a sense.
Michael Kennedy: In that you and I both pulled this Sebastian Ramirez one out.
Michael Kennedy: And I don't really have much more to say other than I want to say for sure.
Michael Kennedy: This is a super nice documentary.
Michael Kennedy: It's super highly produced.
Michael Kennedy: It's done by Cult Repo.
Michael Kennedy: What a bad name.
Michael Kennedy: The comments suggest like, what is this?
Michael Kennedy: like a weird cult or something.
Michael Kennedy: A much better channel name would be Repo Culture,
Michael Kennedy: or Culture Repository, or Repository Culture.
Michael Kennedy: It's something about like,
Michael Kennedy: it covers open source basically, right?
Michael Kennedy: But Cult Repo is weird.
Michael Kennedy: Anyway, it's the same group
Michael Kennedy: that did the one hour Python documentary
Michael Kennedy: that's really highly produced.
Michael Kennedy: So that's all I wanna say about that.
Michael Kennedy: And with regard to the book, right?
Michael Kennedy: For the Talk Python in production book,
Michael Kennedy: I actually started keeping a changelog.
Michael Kennedy: I think we talked to, I think even you brought this up.
Michael Kennedy: Keep a changelog.
Michael Kennedy: Don't let your friends dump Git logs into change logs.
Michael Kennedy: Keep your change log.
Michael Kennedy: And so I'm keeping this for people who are like,
Michael Kennedy: what has changed about the book?
Michael Kennedy: Because at least, well, on Amazon,
Michael Kennedy: Amazon says they will release new versions as they feel like it
Michael Kennedy: if I upload a new EPUB.
Michael Kennedy: Really?
Michael Kennedy: Yeah, but it doesn't say the timeframe of it.
Michael Kennedy: And those should automatically show on people's devices as updates.
Michael Kennedy: And then the Gumroad version, if you buy it directly from me,
Michael Kennedy: obviously I push up new versions and have like numbers.
Michael Kennedy: and my book has a version number in it right which is kind of fun anyway so i'm keeping a change log
Michael Kennedy: following the keep change log style so people can see like do i care do i care about the change do
Michael Kennedy: i need to go back whatever so yeah and i also want to tell people that um it's the it used to be like
Brian Okken: you know several years ago when i did a my first ebook um it was a little little sketchier to
Brian Okken: to figure out how to get a book onto your kindle without um like without going through amazon and
Brian Okken: it's way easier now um if you just like if you grab a book like an ebook for me or from michael
Brian Okken: you can just email it to yourself you can set up a an email address that you just email it to
Michael Kennedy: yourself and it just shows up on your kindle yeah you your kindle gets an email so mine mine is
Michael Kennedy: something with the word paper right in it i don't remember exactly what it is but yeah and it's it's
Brian Okken: totally um you figure it out once and and i've got um yeah it's not bad it's not easy it's not easy
Brian Okken: it is very easy it's not hard so yeah yeah and uh real time follow-up sky as in the same sky that
Michael Kennedy: recommended um typos it looks like 3 14 2 came out just three days after 3 14 1. okay very interesting
Michael Kennedy: all right a couple more extras for me i was on vanishing gradients so that i told you that's
Michael Kennedy: gonna be there that's out that was a very fun episode i a fun chat with hugo bone anderson and
Michael Kennedy: Django 6 is now officially released.
Michael Kennedy: Last week I talked about what was coming,
Michael Kennedy: but the day after we did that, it's now actually out.
Michael Kennedy: So if you're waiting on that, Django 6 is out.
Michael Kennedy: See what it holds for you.
Michael Kennedy: Now, Brian, I think I have a pretty fun joke.
Michael Kennedy: This is a little more elaborate than just a dad joke or something.
Michael Kennedy: Are you ready?
Brian Okken: Yeah.
Michael Kennedy: There's these joke programming languages that actually compile and stuff.
Michael Kennedy: And one that I really love is lolcats, L-O-L-Cats, all one word.
Michael Kennedy: So good.
Michael Kennedy: It actually has multiple implementations of it, and it's good.
Michael Kennedy: But we don't live in the time of lolcats anymore.
Michael Kennedy: That was like an early meme of the internet.
Michael Kennedy: So we now live in a hyper-hyped, crazy headline, overdone age, as you know.
Michael Kennedy: So I present to you the tabloid language.
Brian Okken: Oh, my God.
Michael Kennedy: Are you ready?
Michael Kennedy: Oh, my God.
Michael Kennedy: Here we go.
Michael Kennedy: It's a minimal programming language inspired by clickbait headlines.
Michael Kennedy: Shocking new programming language bewilders programmers at Google and Facebook.
Michael Kennedy: GitHub new headline tutorial.
Michael Kennedy: So let's look at an example here.
Michael Kennedy: Discover how to Fibonacci.
Michael Kennedy: This is import, basically.
Michael Kennedy: Discover how to.
Michael Kennedy: No, this is the function actually.
Michael Kennedy: Discover how to Fibonacci with A, B, N.
Michael Kennedy: Rumor, this is like a try or something.
Michael Kennedy: Rumor has it.
Michael Kennedy: What if N smaller than one?
Michael Kennedy: Shocking development B.
Michael Kennedy: Lies.
Michael Kennedy: Rumor has it.
Michael Kennedy: You won't want to miss B.
Michael Kennedy: Shocking development.
Michael Kennedy: Fibonacci of B, A plus B, N minus one.
Michael Kennedy: End of story.
Michael Kennedy: Expert claims limit to be 10.
Michael Kennedy: You won't want to miss first 10 Fibonacci numbers.
Michael Kennedy: You won't want to miss.
Michael Kennedy: Apparently it's print.
Michael Kennedy: And then I don't know what this last one is.
Michael Kennedy: Experts claim nothing to be Fibonacci of 101 limit.
Michael Kennedy: I think that's like a test or an assert.
Michael Kennedy: Please subscribe and like.
Michael Kennedy: No output.
Michael Kennedy: I'm going to run it.
Michael Kennedy: Hold on.
Michael Kennedy: Run this.
Michael Kennedy: Oh my God.
Michael Kennedy: It runs.
Michael Kennedy: What about factorial?
Michael Kennedy: You won't want to miss this.
Michael Kennedy: Hello world.
Michael Kennedy: Discover how to factorial with n.
Michael Kennedy: Rumor has it.
Michael Kennedy: What if n is actually zero?
Michael Kennedy: Shocking development one.
Michael Kennedy: Lies.
Michael Kennedy: Shocking development n times back.
Michael Kennedy: So good.
Michael Kennedy: Oh no.
Michael Kennedy: Lies is the else.
Michael Kennedy: Yeah.
Michael Kennedy: Lies is else.
Michael Kennedy: Yeah.
Michael Kennedy: Lies.
Michael Kennedy: Because there's an assertion.
Michael Kennedy: It goes lies.
Michael Kennedy: That's like, no, not the assertion.
Michael Kennedy: It's really good actually.
Michael Kennedy: and notice it runs it runs it runs in the browser what is this built on i don't know i'm not sure
Michael Kennedy: if it's WebAssembly or if it's just javascript implementation it's all javascript so okay this
Brian Okken: is awesome it's so good isn't it yeah i think i think we need a uh but you know it used to be
Brian Okken: that this would be difficult but we just have to have the spec for this and we could get like
Brian Okken: clod or something to translate larger programs to uh to tablet i might rewrite python bites the
Michael Kennedy: website in it i think lies exclamation it requires an exclamation mark for lies oh by the way people
Michael Kennedy: were just listening this is all all the keywords the entire language is all caps of course lies
Michael Kennedy: of course anyway i think it's pretty excellent this is old this is old i didn't realize i just
Michael Kennedy: ran across it but uh it's four years old anyway well done well done whoever made this is
Michael Kennedy: amazing this is awesome yeah oh yeah also um uh kiva in the out in the audience points out that
Michael Kennedy: every time you print something it also ends in an exclamation mark even if the text itself doesn't
Brian Okken: have an exclamation mark oh yeah obviously i mean like of course it has to lies this is the end of
Michael Kennedy: the show lies we have more no this is really good it's good so also for people watching the video
Brian Okken: I you'll notice a little less junk in my office I'm starting to clean up after Thanksgiving and
Brian Okken: we'll get there yeah anyway great episode as always Michael thank you thank you everybody
Brian Okken: for listening and we'll see you all next week what if actually this was the end now see you later
Brian Okken: lies