Hello and welcome to Python Bytes, where we deliver Python news and headlines directly to your earbuds.
This is episode 409, recorded November 13th, 2024.
And I'm Brian Okken.
And I'm Michael Kennedy.
And this episode, we've got a couple sponsors, Scout APM and Codeium.
Thank you both of them and listen to their spots later in the show.
If you'd like to connect with us, connect on Fostadon.org.
We're M. Kennedy, Brian Okken, and Python Bytes.
But any Mastodon client gets to us.
And now also Blue Sky.
So I'm trying out Blue Sky.
So we'll drop a link to that as well.
And if you're listening to this in a podcast player, you can join us live sometime on YouTube at pythonbytes.fm/live.
And no need to jot down notes while you're listening, because you can just sign up to be a friend of the show and sign up for our newsletter.
And we will send all the links to you into your inbox every week.
That's right.
The Bytes come to you.
You don't have to come to them.
Yeah, exactly.
So I think we should jump into the terminal this week a little bit.
Yeah.
What do you think?
We absolutely should jump into the terminal.
And I just want to point out, I got a lot of stuff to cover.
I'm on my third cup of coffee, and it's 730 in the morning.
Let's go.
We'll start with something from Will McCoogan.
It's been a while since we've spoken about rich and textual, but the drought is over.
Folks, the drought is over.
This is something I saw Will throw out as a proof of concept.
Okay.
Have you seen this, Brian?
No.
So it's pretty cool.
Imagine, if you will, as I have actually been.
If you will.
Imagine, if you will, that you are SSH'd into your server for a lot of the recent days,
working on something.
And, you know, you've got tree, which is a command that will show sort of a hierarchical view of
things.
But wouldn't it be nice if there was something kind of graphical that you could use to explore
and interact with the file system?
A little bit like Mac Finder or something like Windows Explorer?
Well, that is what this terminal tree is.
So the idea here is, well, I didn't like that.
So the idea is that you run this in the shell and it gives you a tree-like view of, here we
go, that's a better one.
It gives you a tree-like view that you can explore with your keyboard.
It also says mouse.
I don't think that works on Linux, but it works.
It seems to work on macOS.
Anyway, maybe with your mouse, certainly with your keyboard, that you can sort of open up the
tree and go around.
And you find a file, you can hit P to preview it in a little side tab thing, like side by
side with the tree.
You can jump from different roots of this tree by just hitting G and then typing directory
slash apps, enter, and then you're just exploring whatever your apps folder is or whatever.
What do you think?
I think this looks pretty nice, actually.
Pretty great.
Yeah, I was using it over SSH and it's pretty nice.
Now, to be clear, it is a, where does it say this?
I don't know.
Will says, I don't know if this will become a standalone tool or folded back into textual
or nothing, but here, if you're interested, fork it, play with it.
Let me know.
The one thing I was talking to Will about when I saw this was, wow, wouldn't it be cool to
be able to specify a starting directory?
Like, create me a tree of this place.
Right now, it just jumps into your home directory, then you got to navigate from there.
Also, hat tip to, hey, let's run this using uv with a zero install, zero download.
You don't even download textual or this file or anything.
You just run UVX from the get repo and you specify a Python version.
I suppose you could probably drop that, actually.
And then the dash Q so it doesn't output all the, hey, we're creating a rich environment,
all that.
Oh, nice.
Right?
That's the terminal tree as an entry point to this package.
So, yeah, I think if you're looking for a quick way to explore your file system over
SSH, this is pretty nice.
Or even in the terminal on your own machine, although I find that, you know, some people
I'm sure would love that.
It's not how I roll.
I just use binder or an IDE or whatever it is that I'm working with there.
But over SSH, this is handy.
Nice.
Cool.
Mm-hmm.
All right.
I actually love all the terminal apps or the textual apps.
Yeah, there's a lot of good ones.
Yeah.
I feel like we might be heading in that direction again.
Yeah.
So another recent find around textual is this beautiful API client called Posting.
And I got this from Darren Burns.
And actually, it's his project, Darren Burns.
And isn't he part of the textual team?
I think so.
If not, my memory is serving me incorrectly.
But OK, so this is a gorgeous client.
And it's an open source terminal app.
And it's all color coded.
And you've got colorization for the output.
On the left-hand side, you've got collections, which is cool.
You can hide that as well.
But different ways, like if you're jumping to different APIs, like if you're trying different
APIs out, you can have them up in different collections.
But I started this quickly.
I'm like, right before this morning, I'm like, I should try this.
So I'll give it a shot.
And I went down and said, get started.
And similar to like you said, the top installation instructions were to use uv tool.
So that's a uv tool is, and I'm using it now on lots of things.
I think it's a little easier than PIPX.
So that's what I'm using.
So uv tool install, Python 312, posting.
And posting will get you started with this.
And I really loved, I'm just going to go back to the main homepage because it has a lot of
the stuff I wanted to talk about.
It's a beautiful interface.
I was trying it out with the mouse, actually.
I'm on a Mac.
And using the mouse worked great.
I tried some of the keyboard shortcuts, too.
There's keyboard shortcuts at the bottom.
And then the documentation has more that you can just show you how to jump around.
So it is designed to have some quick workflows to work around, like testing an API.
And it works over, since it's termed textual, works over SSH.
It saves stuff.
So when you interact with it, it saves all of your interactions.
And you can save it to a file.
And it's a version control friendly file.
So it's something you can diff and stuff if you want to do it a couple times and see how
things are different.
One of the things I loved about this is when I've tested APIs before, sometimes I've got
a whole bunch of header stuff that I need to stuff into an API to just get it working.
So manual things like, oh, I forget that other one, that manual stuff that you can jump around
and manually fill things out is a little difficult.
But this one has, has the ability in postman.
Yeah, stuff like that.
Where, and it's great for things that don't have, you don't have to fill in a bunch of header
stuff for a post or for a query.
But if you do, this will work great because it's got scripting capabilities where you can
run a Python, some Python code before and after or, and or after a request to prepare the
headers, set variables and stuff to get your, your post ready.
And this is, this is just excellent.
I'm going to be using this all the time.
The colors are gorgeous.
Love the syntax highlighting.
It's configurable.
The key maps, customize, you can even customize the key binding if the ones that they've chosen
for you don't work that way.
That's pretty cool.
But just an excellent little command thing for, or a terminal application for testing your
APIs.
Yeah, this is one of the more full featured textual apps I've seen.
This is great.
Yeah.
So we get from, from Liz in the audience.
I love this thing.
I've been wanting to replace postman for a while.
Nice.
So yeah, I was just in postman today, but I don't want to tell you about postman, Brian.
I want to talk about scout.
Let me tell you real quick about scout APM.
They're big supporters of Python bytes, so we appreciate that very much.
So if you are tired of spending hours trying to find the root cause of issues impacting your
performance, then you owe it to yourself to check out scout APM.
They're a leading Python application performance monitoring tool, APM, that helps you identify
and solve performance abnormalities faster and easier.
Scout APM ties bottlenecks such as memory leaks, slow database queries, background jobs, and the
dreaded N plus one queries that you can end up if you do lazy loading in your ORM.
And then you say, oh no, why is it so slow?
Why are you doing 200 database queries for what should be one?
So you can find out things like that.
And it links it back directly to source code.
So you can spend less time in the debugger and healing logs and just finding the problems
and moving on.
And you'll love it because it's built for developers by developers.
It makes it easy to get set up.
Seriously, you can do it in less than four minutes.
So that's awesome.
And the best part is the pricing is straightforward.
You only pay for the data that you use with no hidden overage fees or per seat pricing.
And I just learned this, Brian.
They also have, they provide the pro version for free to all open source projects.
So if you're an open source maintainer and you want to have scout APM for that project,
just shoot them a message or something on their pricing page about that.
So you can start your free trial and get instant insights today.
Visit pythonbytes.fm/scout.
The link is in your podcast player show notes as well.
And please use that link.
Don't just search for them because otherwise they don't think you came from us.
And then they'd stop supporting the show.
So please use our link pythonbytes.fm/scout.
Check them out.
It really supports the show.
All right.
Next up, Brian, it's good I had a lot of coffee because this, there was almost a first after
eight years, nine years, eight years of the show.
How long has it been going on?
We just had our birthday last week, by the way.
After that, we've never had a straight run of extra, extra, extra as all of the topics.
I almost have too many topics, but I had to have two extra, extra, extras, but they're quick.
So you ready?
All right.
Here we go.
First of all, we have our getting started with NLP and spaCy in Jupyter Notebooks course.
This one is awesome.
If you do anything with spaCy or anything with text and you want to parse it with Python,
spaCy is a great option.
Vincent Orberdam, who used to work at Explosion, actually wrote this course.
So why am I telling you about that?
Because over at Google Forms here, we're doing a spaCy swag giveaway.
So they have a spaCy course with illustrated how-to books and all sorts of other cool things
that you can get around spaCy.
So Ines Montani gave us some codes to give away for people who are interested in that.
So I put a link.
All you got to do is give us your name and email so that we can find you and give you the
code if you want.
So check that out.
Links in the show notes, obviously.
A couple of articles I wrote, Brian, maybe three.
I've been writing a lot last week.
One is I wrote something opposite of cloud native is.
Trying a little bit of a pushback against how many managed services can you have?
Well, let's use Kubernetes.
Oh, and with Kubernetes, it's hard to see the logs.
So we're going to need log aggregation.
And then with log aggregation, we need some log monitoring.
And then on and on, it just builds until you've got this super complicated thing.
And so this article is kind of an homage to like, can we just go back to something simple
that will work for like tons of people?
I think.
So I'm proposing the idea of stack native, like just enough technology to make what you need
your web app or your API or whatever to run, not something that'll tie you so deeply into
all the hyperscale clouds that you end up with a hundred thousand dollar bill, but no idea
how to move away from it.
I almost covered this as one of my topics.
This is a great article.
Did you?
Oh, thank you so much.
That's awesome.
Yeah.
This is a really, really fun one.
Related.
I also wrote, and I talked about it last time, but I wrote this up that we, Python Bytes,
Talk Python, Talk Python Training, all the APIs, et cetera, et cetera, in like a broad sense,
have moved to Hetzner.
Remember I talked about how Hetzner was really interesting and appealing and hey, I took
the plunge, bought us a, I splurged, Brian.
I went for the big VM, the big machine.
Okay.
Eight virtual CPUs, 16 gigs for a whopping $25 a month.
That is $112 at DigitalOcean, $205 at AWS and $320 a month on Azure.
Same machine.
Okay.
And if you look, the performance, people are saying, well, it was probably cheaper because
it's like from 20 years ago or something, CPU performance, 1.2 times faster than DigitalOcean's
$112 version.
And the bandwidth is eight times more, one gigabit bandwidth versus two for $25.
So anyway, this is really, really excellent.
And talked a lot about that.
So another thing I did is I created, I was on, I was on vacation for four days, long weekend.
So I decided to create a package for Chameleon and Flask.
Chameleon, the web templating language.
Flask, you know what Flask is.
Yeah.
Usually it uses Jinja.
I don't like Jinja very much.
I think it's too much Python and not enough pure web, not like view or other things where
you just have little attributes.
Chameleon is like that.
I like it a lot.
Plus I have a whole ton of Chameleon templates I don't want to mess with, but I want to do
some Flask things with some of that base.
So I created a package that if you just put a decorator onto either a async or a regular
non-synchronous view method in Flask, it will, when you return a dictionary, it'll use that
dictionary to render the Chameleon template.
It's pretty awesome.
That's neat.
And if anyone wants a really cool example, there's some of these that have existed before,
but they were super simplistic.
Like, okay, so technically the Chameleon engine is set up, but then you have to do every view,
you've got to do all the manual steps to actually render it, or it only works with synchronous
functions and not async.
So here's a decorator that looks and sees if it's decorating an asynchronous or asynchronous
function and creates a different wrapper behavior.
So the wrapper itself is async or not async, depending on which it covers here.
So if people are trying to write something regardless of whether it's web or not, that can
handle both sync and async, here's a little example for them.
Okay.
All right.
Next, also released a new version of Lismunk, the email API client for Python.
I think, I have, what's the guy's name?
Ron.
Thank you.
Ron Hudson did a bunch of work adding new features to that.
So that is out.
Also-
You're still on the go-over.
What's up with that?
Well, it's only been out a couple of days.
Okay.
I feel like I should give it a week.
I'm just now rewriting.
I've been doing a bunch of work the last day to use that to convert something into Flask.
I'll talk more about that later.
And there's been like little tiny issues.
I want to get it a little bit more.
I want to test it for a week before I give it a non-dover.
Come on.
Okay.
That's fine.
Okay.
Yeah.
Oh, and Ron is out in the audience.
Hey, Ron.
Awesome.
Thank you, man.
Thanks for the help.
Okay.
So on here to TOB.
We all know TOB, TOB index.
There was big news.
Hey, guys, what?
Python's number one.
Hooray.
In this other way, right?
We just talked about GitHub last week and TOB.
This is not news that Python is number one, but it was updated for year over year in November.
And I just noticed, look at the numbers here.
Python is not just number one over C++, then over Java, over C.
It's over two times as popular and has a almost 9% year over year growth.
Whereas number two, C++ has 0.3% and Java's 1% and C is negative 3%.
C# has negative 3%.
So not only is it number one, it's double and is growing many times faster than anything else
on the list, including Rust.
That's amazing.
So I'm not sure if we should really bet our careers on these toy languages yet, but you
know, you guys do you.
Okay.
I'm betting my career on it, baby.
A little late.
So update on PEP 750 being spearheaded by Paul Everett and others.
I just talked about Jinja versus Chameleon.
Yeah.
But these are all external packages that have their own parsers, their own behaviors.
And wouldn't it be nice if Python itself had a type of a template language?
Maybe.
Sure.
Maybe.
Well, I mean, we have f-strings.
We do have f-strings, but when you're doing things in, say, I want to create the content
of an HTML page in memory as part of some action, right?
A lot of people say, well, I guess we could run, like set up the Jinja engine or whatever.
So this PEP 750, which is in draft mode currently targeting 314, is trying to bring some modern
version that's like f-strings into Python.
So this is interesting coming along.
Progress is happening there.
Cool.
Switched over to Canary email, Brian.
I got so sick of Spark and all of their, hey, we're only focused on building AI features.
Even though Canary says it's your AI email copilot, they actually seem to be working on features
that are not just AI, even though that's what their landing page seems to say.
So that's an interesting experiment I'm running, but not as interesting as a couple others that
are coming up.
Omnivore.
Remember I told you they're shutting down and deleting everybody's account?
Yeah.
All right.
So I thought, well, let me go back to Pocket.
Pocket supports Firefox because it's owned by Mozilla.
That's kind of cool.
And I had a paid account to them.
So that's great.
And then I realized that Pocket kind of represents everything that's wrong with Mozilla on a broader
scale.
And it made me sad.
So for example, I told you I just took this four day trip.
I'd like to take some things and take it with me and maybe read it on the plane or at the
beach or wherever.
Yeah.
Pocket has been around for 10 years.
They were acquired by Mozilla in 2017, I believe it was.
They don't even support offline mode.
You can't even read the text offline like an ebook.
It's like acquired in 2017, put on the shelf, worked on other random things that have nothing
to do with Firefox or other things they're selling.
Right.
Anyway, made me sad.
Went through a whole bunch of different other things.
I'm back at Instapaper.
Instapaper is actually really great.
The only thing it's not great at is read it to me, which is what Omnivore was so perfect
at.
But you know what?
They're dead.
So I will not speak of them ever again.
Anyway, Instapaper is actually pretty awesome these days.
So I know a lot of people are talking to me on Mastodon and other places.
That's where it's at.
So other people are saying they like it or don't like it?
Well, no one really mentioned Instapaper one way or the other, but there's good links.
There's Readwise.
There's like a bunch of other premium paid ones that are just, they're not that great,
but they're expensive, like $100 a year expensive.
So I don't know.
I tried them.
Instapaper is more.
So I started, I used Instapaper a long time ago and I don't remember why I stopped.
I don't remember why I stopped either.
But, well, I know I would switch to Omnivore because it was awesome, but it's gone.
So say lovey.
Anyway, onward and upward.
If you are feeling the open source self-hosted world, there's Hoarder.
I mean, who doesn't want to be a Hoarder, Brian?
But this is really awesome.
It's kind of a save your links and notes and articles and then let locally running AI tag them
and group them and this thing just, it's a Docker run, open source.
It's pretty awesome.
But I do not need more self-hosted things to babysit and backup.
So not messing with it.
But people, they really want, this looks pretty neat.
All right.
We're getting close to the end.
I promise.
Yeah, this is the last one.
So have you heard about the Arc browser?
No.
Super minimalist wrapper around Chrome like Vivaldi.
But it's all about like reimagining the web and it's, you don't even see the address bar.
You just hit a command palette and then you type the, type the address you want.
And it's just, it's magic.
And well, if you wanted to, I don't know, take the, the most extreme caricature of a Silicon
Valley bro, the person running Arc is that.
Okay.
There's some amazing, there's some amazing videos in like a cringy way of, so they made
Arc and it became incredibly popular amongst the people who liked it.
Like it was going really, really, you know, the adoption was going very fast and they decided
we want to build a browser.
It's really based in AI and you don't even need to tell it what you want to do.
It just browses the web for you.
You're just with it.
Like seriously, that's their new project.
And they're kind of like, oh, we're done with this Arc thing.
We're going to go build something that browses the web for you.
So a bunch of people are like, ah, what is there?
Well, it turns out that someone, some group was working on this thing called the Zen browser.
Now I knocked on Mozilla before this is based on Firefox and it's awesome.
Okay.
So this is a super minimalist wrapper that gives you a really clean, nice, just let me
see the web.
You know, Chrome was called Chrome because it literally maybe should be anti-Chrome.
It took away the window Chrome, all the junk that used to be around all the toolbars and
buttons and everything.
And it minimalized it.
But this is, you know, the next version of that.
And it's, it's super neat.
So in fact, that's what I'm running right here.
And you can see all the, all the things you can see the little tab bar on the side, but
you don't even have to have that there.
And isn't this nice?
Sure.
It's cool.
Yeah.
So anyway, I'm giving this a try.
It's, it's quite promising.
The people working on it are releasing versions a couple of times a week.
So it says alpha, but it's working pretty well.
So anyway, I do want to shout out like one of the features of the Arc browser is that whenever
you look at a picture of an animal, you see two.
Yeah, exactly.
Of course, because how, how else are they going to go on the Arc?
Yeah.
They're not allowed in if there's just one picture of them.
No, that's pretty good.
Okay.
So I recommend Zen dash browser dot app.
It's, it's pretty awesome.
Right now it doesn't have a built-in ad blocker.
And if you go to a site that's got a bunch of ads and you somehow block them with say DNS
or whatever, they'll leave big gaping holes as did Arc.
Unlike Vivaldi, which takes them away.
But I talked to the Zen browser people and they said that they are very soon releasing
a feature that cleans up this page.
So it's not just pages with holes where there used to be ads, but a clean page.
So anyway, if you're wondering about that, that is coming.
I'm still pretty happy with Vivaldi, but I know.
Go for it.
I'm experimenting, but I'm also still a big fan of Vivaldi.
So this does have the drawbacks that Firefox itself has in the sense that certain pages don't
behave as well based on Firefox, right?
Because it's really Firefox at the core or Gecko or whatever they call the rendering
engine these days.
Okay.
All right.
Over to you for your final item.
Yeah.
So for my final item, I wanted to talk about uv.
So we actually talked about uv twice at the beginning of the show, talking about how uv install
or uv tool install works like Pipex.
But there's an article about from Jeff Triplett saying uv does everything or enough that I'm
not sure what else it needs to do.
This is a great title because that's how I feel.
I mean, uv is I it's kind of refreshing that I need to forget about a lot of things.
And I these other projects are still great, but it solves so many problems.
I'm just going to read here.
UV feels like one of those old infomercials where it solves everything, which is where
we have landed in the Python world, like it slices, dices at Julian's.
So I've had several discussions with friends about uv.
And even when we talk about it during my weekly ish office hours, the list has grown.
And it starts to sound like not just what can it do, but when it's a shorter list to say
what it cannot do.
So let's just come up with some.
He has a list of things that I think are great of how it's replaced things.
So uv pip install replaces pip install.
Not completely, but yes.
Yeah.
I am now using that almost exclusively.
UV V ENV replaces the Python dash M V ENV.
And I'm using that wherever I can.
So, yep.
Using that uv pip compile replaces pip-tools compile.
Pips uv pip sync replaces pip tool sync.
UV run replaces pip X.
UV tool run replaces pip X.
And like we talked before, uv tool install does the installation of tools as well.
UV Python, actually, we covered that on the show, but I haven't really been using that
very much because I use virtual environments.
And a virtual environment just installs Python for me if it's not there.
So that's what I've been doing.
Yeah, it's super awesome.
I don't find I use it very much locally, but I do use it in Docker when I got to get Python
into a Docker image.
It's a nice way to do that.
Cool.
UV build, which was new to me, or I forgot about it.
We'll build your package for PyPI and uv publish publishes it.
I just, you know, I told you I published those two packages, the chameleon dash flask and then
the list monk one.
Yeah.
Both of those uv build, uv publish.
Perfect.
And what I find is I'm using these like on new packages.
I'll do uv.
I'll do build and publish until I get the workflows going because after a package is, you know,
around for a little bit, then I do a GitHub workflow that will just do a build and publish
on with a version.
When I push a version, it does that for me.
Nice.
So there's that.
And then we talked about this GitHub actions with setup uv.
Is there Astral has a setup uv for bringing uv into GitHub actions to make that faster?
And then there's a Docker thing bringing uv and Python to Docker.
I haven't.
Have you used this?
Have we talked about this?
No, I believe it uses multi-layer Docker builds where you have a build image and then you have
the destination image and it gets that one and it copies it into the actual running image.
But I have a base image that just does the curl install and it barely ever updates.
So it's fine for me to just do it that way.
I haven't messed with this.
And so I liked the idea where poetry was going a while ago with trying to have like kind of
a unified project feel for, you know, to have these project files.
But I wasn't ready for it then.
But now that I've converted everything to pyproject.toml, having that as my project file makes sense.
And uv has add, remove, sync, and lock that do things that are project related.
So adding a dependency to a project, removing.
So it'll add to pyproject.toml, remove, sync.
And I'm actually finding I'm using this a lot.
So I'll create a, so I'll clone a project, create a virtual environment, and do uv sync.
And it installs everything that's in the project.toml or requirements file suite.
So uv sync is awesome.
Yeah.
So then he talks about what does it not do?
And does it run custom scripts defined in your project.toml?
Oh, OK.
There's a few things it doesn't do.
It doesn't manage bumper and bump versions like bumper.
There's so many ways that people do versions of it.
You know, do you have a bumper sort of a thing that you use, Michael?
Because I used to.
I used to use a couple.
But they were more complicated.
I mean, it was just an extra thing.
And I thought all it's doing is changing a number for me.
I can just do that.
Exactly.
No, not really.
I have one that sort of keeps track of how many deploys or pushed to productions I have for certain things.
But it's kind of meaningless.
So short answer, no.
I love the last item.
UV doesn't replace Python.
Nor should it.
But I am.
I'm really, you know, I don't even feel bad that I'm using uv in all the places where I can.
Because why not?
I am your father.
No, I don't feel bad about it either.
I love it.
It's revolutionary in how quick it does things and how comprehensively it does it.
Especially getting Python versions onto your machine and creating virtual environments with different versions of Python.
It's glorious.
Yeah.
All right.
Before we get to our extras, there are any other extras.
No other extras, except for we have an extra sponsor I'd love to tell people about.
This portion of Python Bytes is brought to you by Codeium, the AI tool of choice for professional software developers.
That's C-O-D-E-I-U-M.
Codeium removes tedium from your development through a suite of state-of-the-art AI capabilities available with extensions in all of your favorite IDEs.
Use Codeium in VS Code, the JetBrains IDEs, including PyCharm, Visual Studio Proper, Eclipse, Xcode, NeoVim, Jupyter Notebooks, and more.
Uniquely, Codeium is fully enterprise-ready with over 1,000 paying enterprise customers, including multiple regulated Fortune 500 companies in completely self-hosted air-gap deployments.
Join over a million developers and use Codeium for free forever.
Once you see the value, then it's time to ask your company to consider a free trial of the enterprise plan.
To learn more about Codeium and get started today for free, visit pythonbytes.fm/Codeium.
That is pythonbytes.fm/C-O-D-E-I-U-M.
Don't forget the E.
Or just click the link in your podcast player's show notes.
Thank you to Codeium for supporting Python Bytes.
Absolutely.
So no extras.
I got an extra.
Wait, you got extra.
I have no extras because I am still out of breath from covering all the extra extras.
Yeah, the extras.
So I wanted to just, there's a little article from Ned Batchelder, coverage.py originally.
And it's, what I thought was, I always wondered why it's called coverage.py.
Is it because it's like all the stuff on PyPI is Python.
So why .py?
Well, it used to be one line of code or one file, not one line of code.
But it was originally a single file.
So the coverage.py name was literal.
It was a name of a file and it had only 350 lines of code.
And it was written by Gareth Rees in 2001.
And Ned started maintaining it in 2004.
So a few years later.
And he still will tell you, I didn't invent coverage.py.
I'm just maintaining it.
But he's maintained it for all but three years.
And now it's 20,000 lines of code and about 100 files.
So it's, and it's got twice the amount of C code as it originally had.
And it's almost 20 years later.
Ned's still pushing the ball forward.
So we appreciate that, Ned.
And that's why it's called coverage.py.
So that was it.
Yeah, very cool.
The other extra.
20 years.
Ryan.
20 years on a project.
Yeah.
That's awesome.
And we couldn't ask for a better maintainer for this project.
So Ned's awesome.
The other thing is there's a lot of, there's been some news lately about people wanting to shift from what used to be Twitter and now is X.
And go to, a lot of people are going to Blue Sky.
I'm trying it out myself.
So if you're over on Blue Sky, connect with me.
And we'll play with it a bit.
See if we want to do something else for the podcast or not.
All right, cool.
You might drag me over there.
I'm not there yet.
But on the Mastodon and the others.
One of the things, I was going to try to find this article, but I can't find it.
There was an article saying that a year ago, or even just a few months ago, there were so many millions of people on Blue Sky.
But none of them were very active.
Like me, I had an account, but it wasn't there very much.
And it sort of feeds on itself, right?
It's a network effect.
If you talk and nobody says anything back to you, it's not fun.
But now it's got a huge growth.
Even Taylor Swift said she's switching over to Blue Sky.
But there's a lot of Python people there now, too.
And it's not just an echo chamber.
The people are actually hanging out and replying and stuff.
So it's getting fun there.
So just letting you know.
Awesome.
And that was my extra, really.
Go follow Brian in the sky.
Yeah.
All right.
Ready for a joke?
I am very ready.
I am.
Also, a quick shout out to the Momentum extension, which gives you a cool little homepage with all sorts of fun stuff you want.
Oh, that's on your New Zen thing?
Yeah, but you can get that in Vivaldi.
You can get that wherever.
Yeah.
Okay.
Yeah.
Very neat.
And a bunch of cool little hot links.
But that's not funny.
No.
Sleeping is funny.
How about how programmers sleep?
We talked about how they sit in chairs last time.
We're down to the basics here, Brian.
Okay.
But I think many of us will relate to this.
So there's a picture of a programmer, cat, sleeping.
Earthquake.
Still asleep.
Thunderstorm.
Still asleep.
Alien attack.
Pew, pew.
Still asleep.
Remembers how to fix that error on line 56.
Boom.
Shoots out of bed.
God.
It's three in the morning, but I can fix it.
Yes.
Definitely.
Liz says, I'm in that picture, and I don't like it.
Okay.
Sort of related.
I got to tell this story.
Last night, I was writing up an article on, not an article.
I was explaining to some of my sponsors how some requirements cannot be implemented.
And I listed out the reasons why the implementation is not possible.
And then at the end, I'm like, either we don't do this, or we move the database out of one of the objects.
Well, we can move.
That's fine.
I saw it.
It's possible.
Yeah.
So sleep or writing it down helped to figure out.
Yeah.
Or even just going for a walk or something.
I would do that a lot when I get stuck.
When I was earlier in my career, I'm like, it's time for a walk around the building.
I'll be back in 10 minutes.
And also, yeah.
Wait, I'm babysitting a kitten right now, and he's not letting me sleep.
So he might be sleeping through a thunderstorm, but I'm not sleeping through the kitten.
So anyway.
Very meta.
I think we got to leave it there.
What do you think?
Yeah, let's stop talking.
Thanks again, Michael, for a wonderful episode.
Bye.
Yeah.
Thanks as always.