Hello and welcome to Python Bytes, where we deliver Python news and headlines directly to your earbuds.
This is episode 398, recorded August 26th, 2024. I'm Michael Kennedy.
And I'm Brian Okken.
This episode is brought to you by us. Check out our things.
Brian's assorted pytest courses, his book, the almost 300 hours of courses over at talkpython.fm.
So many things that you can do to support us and get awesome stuff back in return.
If you want to connect with us on the socials, check us out over on Mastodon.
And we're also on X under very, very similar usernames.
You can find us in all of the places.
And of course, comment on the show on the YouTube stream, which is linked from the episode page all the time.
And with that, Brian, how shall we start today? What do you got for us?
Well, I've got some open source myths, but I wanted to touch on the day early bit, I think.
Oh, yes, that's right. Because we are recording on Monday. This is not Tuesday.
In fact, I looked at my watch, which has a little calendar, what's coming up next on Sunday.
And it said Python Bytes. I'm like, huh, that's weird. I feel like it's, I thought it was Sunday.
It even caught me off guard.
But no, here we are.
Yeah, my work schedule changed a little bit. And I got to go into work on Tuesdays and Wednesdays now.
So we've moved the recording to Monday. That's just, that's the long short of it. Luckily, Michael has a fairly flexible schedule.
Indeed.
And that's the plan going forward, right?
So until your meetings change again, for whatever reason, or you got to do trips, we're going to plan on doing it every Monday, 10 a.m. Pacific time.
Yeah. And we'll get to that a little later. We've got a little cheat sheet for people to be able to look up when it's going to be recorded.
Oh, indeed. Very cool.
Okay. So our first item, though, I just wanted to talk about how awesome open source is. I'm working on open source software.
And I was, there's somebody named Josh Bressers on Mastodon, posted a list of open source myths.
So myths about working in open source or using open source.
And he started the list. And then on Mastodon, like, let's see, most projects have more than one maintainer.
Yeah. Usually it's just one, which is, yeah, surprising to me also.
So let's see. I like these two together. Open source is more secure than closed source and open source is less secure than closed source.
So both, both at the same time, they can exist.
And so, and then he said, got any others and a whole bunch of people sent him back myths.
So he has a, let's see, a list on, he put it up on Google Docs.
And I made a copy because I wanted to highlight a few of them because I thought it was, they were interesting.
So a few I want to call out. Most projects have funding driving the development.
Yeah, no. Does anybody think that? Anyway.
If the source code is available, it's open source. No, it's not.
And that's something that surprised me too.
Just because it's on GitHub even doesn't mean that it's open source.
You can publish your proprietary code online if you feel like it.
People are probably going to copy it anyway if you publish it, but it doesn't have to be open source.
Yeah.
It has to do with the license, right?
Yep.
Yeah. So most of the time I have, I've been one of those people that just defaults to MIT because, because I read it once and it went, oh yeah, it sounds good.
Basically MIT is what it's kind of like open source, but it's open source, but you can also, you can also use it in commercial software if you want to.
And some of them, some of the licenses don't allow that.
So my favorites coming up, all open source developers live in Nebraska.
I thought it was just one.
I thought there literally was one open source person in Nebraska, according to XKCD.
Nebraska.
Oh yeah.
Is that the XKCD thing?
Yeah.
It's like we have this huge castle of everything supported by one person, single open source developer who lives in Nebraska.
I believe that's right.
So, so Marco says, hey, I don't know if he's upset about not being in Nebraska or being the one developer in Nebraska.
Not sure.
So I thought it was Kansas because aren't all the Django people in Kansas?
Yeah, Lawrence.
And then let's see, all open source is run by hippies?
Sure.
Wait, but it's in Nebraska and hippies aren't in Nebraska.
So, or maybe they are.
Are there hippies in Nebraska?
I don't know.
Never been there.
Open source means it costs $0.
Well, you can use it without paying, but it doesn't cost zero to make it.
Everything is being rewritten in Rust.
It does seem like that lately, but no, there's a lot of stuff that's not good.
Well, we'll talk more about that one later.
Yeah, I guess that's a decent segue.
But no, this is a cool, a fun list of some of them are useful items.
Open source makes you rich.
No, it doesn't.
Well, maybe it makes some people rich.
It hasn't worked for me yet.
Yeah.
Anyway, fun list.
So thanks, Josh, for putting this together.
Yeah, that's a really excellent one, actually.
I love it.
Okay.
On to my first item.
Got a bunch of things that I'm going to cover, and I know you do as well, Brian, this week.
So some of them will go fast, some we'll dive into.
Mostly we'll go fast through them.
So this one is a feature capability framework matrix for people who do functions as a service, or aka serverless.
Right?
I am, I'll go on the record and say I am somewhat skeptical about the usefulness of serverless, but I know for some people, for some of their setups, they absolutely love it.
And certainly for you, there are tons of interesting use cases around serverless.
All right.
Certainly the most common one is Lambda, AWS Lambda, I would say.
And we also have Azure Functions, which is the serverless thing that lives in Azure.
We previously talked about Cloudflare workers.
And what's cool about the Cloudflare workers is that they run on WASM or WebAssembly.
Now the WASM ones start to get really interesting to me.
So if I've got a Docker container in AWS and it spins up every time there's a call, one of my functions.
Okay.
Interesting.
Maybe I should just have a Docker container running instead of like a bunch of start, stop, start, stop, start, stop.
And sort of a funky pricing you're not really sure about.
There's a pricing chart you can get into.
But the reason I really thought this was interesting is there's a couple of them that run on the client.
As far as I know, there's not necessarily even a per usage fee there because it's running not on their infrastructure.
It's just shipping some bytes.
So one of them, we talked about Cloudflare.
Another one I want to talk about is from Permian.
This is Python 3.11 Plus.
And if you scroll over, hiding in the side, there's a link.
There's this thing called Spin.
I don't know if you've heard of it, Brian.
I've never heard of it.
No.
Spin Python SDK.
So it says, we'll look at how to build a serverless app using Python and deploy it to Fermion Cloud in a few simple steps.
And it talks about how all this stuff works.
It's based on a plugin called Py2Wasm.
And by the way, this may run in their cloud.
I can't remember this because you can run Py2Wasm.
You can run Wasm code locally or you can run it in the browser.
Right.
So it could go either way.
But basically, this gives you a WebAssembly super lightweight foundation to run Python code.
For your app.
Which I think is pretty awesome.
So here's this grid.
The news item is this matrix of these comparisons.
But some of them that it points out here are based on Wasm, which is pretty interesting.
The Fly.io one is based on MicroVM.
It talks about which frameworks you can use.
Do you directly program it?
Like FastAPI for Cloudflare or Spin for Fermion.
Lask for Google.
A lot of interesting stuff here and how to process it.
And then also the pricing.
Yeah.
This is actually timely because I have a project that I was thinking about doing some Lambda functions and things like that.
Yeah.
Was it last time or the time before where I highlighted something where someone had gotten like a $96,000 fair sale bill?
We're doing some of their processing.
Yeah.
That'll catch you off guard.
So you want to know what you're in for.
And this is a nice comparison.
I think it's pretty neat.
It's really, you know, I don't know why it has to be so complicated.
Like the Google one is $0.40 per 1 million requests plus $0.0000025 per gigabyte per second.
Is that where?
Yeah.
And then some more for CPU and then some more for egress.
You know, like, wait a minute.
Like others are based on memory.
It's just like it's really hard to understand.
I don't know.
But that's how it goes.
Wait, what's egress?
Data out as opposed to data in.
I thought they were type of bird.
Yeah.
Well, it usually lives like right above fiber optic cables.
And it goes only away from data centers.
That's its migration pattern is away from data centers.
So $0.12 per egress.
Yeah.
They carry a lot of data on them birds, though.
It's okay.
Yeah.
So that's why I like to have most of my data go underwater.
There's no birds.
Yeah.
So people could check this out.
They would.
It's just a GitHub repo.
You can obviously make contributions and add stuff and so on.
Huh.
That's pretty cool.
Nice.
Yeah.
All right.
Back to you.
Okay.
Well, we have talked about this top PyPI packages before.
I'm pretty sure.
From HugoVK.
It's just a list that's updated.
I don't want to call out Hugo too much, but it's supposed to be updated monthly.
And it was last updated in July.
Yeah.
Maybe we get some August updates.
Anyway.
Well, maybe he's traveling near relative ballistic speeds.
In which case, that would explain it.
Oh, yeah.
Maybe.
Okay.
Anyway, that's close enough.
So, you know, it's a month old, but that's all right.
Anyway.
So there's a list of it shows the top 100 right away.
But you can show the top 8,000.
So what are the things I've used this before is to try to find the top pytest plugins.
So I'll grab this data or I'll like, you know, show the 8,000 and then I'll like search for pytest.
Just pytest.
Because most plugins are pytest.
So the top one's going to be pytest.
And then the next ones are like, you know, the plugins.
Because they often have pytest in the name.
It's handy.
So I thought it'd be cool if I just did something about this and made my own list.
So I did.
This weekend, I decided to give it a shot.
I wrote top pytest plugins.
And I just grabbed the top 8,000 because it's available on GitHub.
He just publishes the top 8,000 all the time.
Once a month.
You can grab those as a JSON file and parse it.
So grab that.
And then I'm listing.
I just grabbed all the pytest things with pytest in the name other than the top other than pytest.
And I grabbed.
There's 142.
It's basically all 8,000 and however many.
So 142 plugins show up in the top 8,000.
I thought it was cool that pytest check shows up.
That's my little plugin.
Made the top 25.
Yeah, it's at 25.
So that's cool.
Yeah.
And a bunch of that I love in here.
There's actually some pretty cool stuff that I want to explore more by looking at this.
A lot of the top, like the top 10 or so, they don't change much because you've got tons of projects using them.
Even though pytest runner, come on, people.
pytest runner should not be the number second one because it is deprecated.
It's so that you can run pytest tests from Python setup.py test.
And like, who does that anymore?
I don't know.
I thought everybody was.
30 million people did that.
Yeah, apparently.
So anyway, I thought it was fun.
The downloads.
So top PyPI packages just gives me the name and the download count.
So I wanted to know like how to get the summary on there.
So I asked on Mastodon and Jeff Triplett delivered.
And he said, hey, why don't you use the API from the warehouse?
Yeah.
PyPI is built on warehouse and warehouse has an API.
So you can use it to get some interesting information.
So I did that.
And that's how the summaries come in.
I wrote up a blog post about it.
So that's linked about how this is done.
And then what?
Publish the code also.
So you can check it out.
And then I was like, it's dumb code.
Why?
I'll publish it anyway.
Why not?
And Jeff Triplett says, yeah, it needs cleaned up a bit.
So he threw it into Claude 3.5, 3.5.
And came up with what Claude says is the better code.
So anyway.
He also added Rich.
So I have to incorporate this.
Rich and Typer.
Yeah.
He added Rich and Typer, which really didn't add much code.
So ooh, green.
He did the download count in green and the packages in magenta.
And the what?
Oh, the download counts are in green.
And the number is in cayenne, cyan.
I don't know.
So thanks, Jeff.
So anyway.
Yeah.
Very cool.
I love it.
Now, just one more request for your blog post there.
Would it be cool to see a graph of popularity?
So you can sort of see what does the tail look like in terms for...
So you can see it tail off pretty quick.
But as a picture, how would those numbers look?
Oh, yeah.
Okay.
So a graph of popularity.
That'd be fun.
I wanted to see...
There's a couple other things I wanted to see, like the which Python version that it supports.
And I also kind of want to dig in a little bit to see which ones it's tested against.
So if there's some way to look into the code to see it supports 3.8 and above often.
But is it tested on 3.12 yet?
Sort of things.
Yeah.
Interesting.
Does it support free threading?
Yeah.
I don't know.
The other thing that I thought would be cool was...
Somebody requested this on Mastodon.
Some trending for keeping track of this over time and seeing some deltas.
Like, which ones are going?
Like, upward trends or downward trends or something?
Oh, yeah.
Yeah.
That would be cool to see where the momentum is for them.
Yeah.
Oh, one of the things I did want to shout out for Jeff, his version of this does...
It also takes the package name as an input.
So you can, if you wanted to look for things with Django in the name or things with, you know,
something else like Jason in the name or something, you can search for those as well that way with his.
So often...
Excellent.
Yeah, yeah.
That's super cool.
And Henry out there says, a badge given the rank would be fun.
Given the rank.
Like that...
So you can put it on your GitHub readme.
It's just like number 26 most popular pie test.
Oh, yeah.
Plugin.
Something like that.
I'm reading into this, but that's what I think.
Yeah.
Star count.
Skip.
Star count.
Does that matter too much?
Yeah, perhaps.
All right.
Derivative of star count.
Is it going up?
Like, how fast?
Anyway, let's carry on.
You're going to have a whole master's thesis.
We could definitely bike shed this for a long time.
We could.
Yeah.
We could.
Okay.
Let's hit the big news of the week.
Big news.
Yeah.
I swooped in.
I know you're going to cover it as well.
I learned you were going to cover it after I grabbed it as a topic.
So this comes from the astral folks and Charlie Marsh.
And maybe I'm going to have Charlie on Talk Python and me to cover this tomorrow or in a week.
I'm not sure.
He's traveling, I think, or something like that.
So we'll see if we can make it happen tomorrow.
But very soon, Charlie's going to come on Talk Python.
I'm going to dive in deeper into this.
But let's spend a few minutes on it.
Here's the announcement.
The official announcement is UV.
We've talked about UV before.
It's started out as kind of a pip replacement, but it's growing to do more and more things
now.
And the announcement is UV, a unified Python packaging.
So there's been a lot of trends in Python packaging about tools that disintermediate PIP
and some of the other things we do with lock files.
And there's sort of been two takes.
One take is we build stuff inside Python.
Then once we have Python and we have this tool, then we manage our projects.
You know, I'm thinking of things like Hatch or poetry.
On the other hand, there's been things that try to manage Python from the outside.
And probably the most well-known one is Pyenv.
Pyenv, not Pyenv, Pyenv, which gives you your Python or maybe Knox talks for testing and it'll manage
the Python and the environments.
And so they're coming, Charlie and Astral are coming at this from that outer, outside perspective
more, right?
Here's a tool that doesn't depend on Python.
And until recently, it's been a fast way to do pip things and pip compile and so on.
But now this is a big, big announcement for here is the thing that can kind of be Cargo.
Cargo is the Rust version of this.
I think there's a lot of inspiration for a lot of people around that.
I don't use Rust, so it doesn't inspire or disinspire me.
It just, whatever.
But here's the thing.
It has end-to-end project management, so you can add dependencies, you can run tools
against your program like pytest or whatever.
It can create lock files, it can update those lock files, it can install Python.
We talked about that last time, right, Brian?
Yeah.
So UV Python install or UV Python list and all those options.
It can now run scripts, which is pretty interesting.
So if I gave you a single Python file and like Jeff Triplett's example, it depended upon
HTTPX and I gave that to you and said, hey, Brian, run this.
What would you do?
You'd be like, try to run it.
No, it doesn't run.
I guess I need a virtual environment or I'll just into my system, install HTTPX and then
it's going to need another and so on.
That's a hassle, right?
So with the script execution thing, what you do is you put into somewhere, into the top
of your file as a multi-comment.
It's a hash and then it has four slashes.
I don't know.
Meta comment within a comment.
You put a comment here that says what this library depends upon and then theoretically you
should be able to run this.
So if you say UV run and you give it the script, it'll look at that and say, oh, I'm going to
need to quick install or find the cached version of what's listed at the top of this.
So as long as you had UV, I could just give you any file.
You could run it and that could be a cool distribution mechanism throughout like your company or utility
tools where at least you've agreed upon UV as a basis.
It's pretty cool because it even create, I think this one even creates a little virtual
environment to install stuff and run.
It, yeah, all this stuff has a lot to do with virtual environments and I don't know if it's
a persistent virtual environment, but yeah, it does isolate these things.
And so there's two ways, the reason I'm not certain is there's two ways to do this.
Like you can create a project and start it, initialize it or sync it and get it going.
You can also create virtual environments here with UV and it'll go and create one of these
based on say the pyproject.toml or something, but you can also run commands.
There's ways to just run like the tooling stuff that they're doing.
And when you look at that, it will use it.
I don't think it creates a virtual environment, but it uses the cached versions and just runs
in kind of an isolate.
So it's, if you say UV tool run, which is alias to UVX kind of like NPMX, it uses an isolated
environment, but yeah, exactly.
The environment doesn't last.
Right.
Whereas if you say UV tool install versus UV tool run, there's like variations about this.
Right.
But, but the gist of it that like as a user, it's not, it's not, it's not throwing stuff
into my global Python, which I want.
I don't want that.
So it's doing the right thing.
You might, I might not know what it is, but it's not like polluting the global Python.
Yes, absolutely.
Yeah, exactly.
It does the right thing for you.
And it does it super, super fast.
Like I was checking out an example and after you've run it once, after it's basically cached
the dependencies, it's instant.
It's as if those things were just there, right?
As if you were in an activated virtual environment and good to go.
Yeah.
I'm really, I've, I've been changing my workflow over to all of this, especially since, so that
we did kind of cover it last week, but all the, all the, the neat things that I saw in
UV were all like, like experimental.
They're not experimental anymore.
They're all, they're all locked in.
So.
Yeah.
Yeah, absolutely.
This is the big, big release we have in the audience.
Makeshift says super into UV primarily for Python management, interested in script execution
and packing that up into something that acts like a single binary executable.
Yeah.
It kind of does give you the sense of long as you're connected to the internet, here's the
thing that's always ready to run all versions of Python, all dependency, you know, regardless
of the dependencies or regardless of the version that it says, assuming that it's in the
UV Python list listing, you can just run it.
Right.
And if it's not there, it'll download it.
But if it is there, it'll use the cache version and off it goes, which is pretty awesome.
Yeah.
You bring up something interesting that I haven't tried is like, if you run, run all these
tool chains for a while and you disconnect from the internet, what happens to you?
I think if it's cached, it's okay.
But if it's not cached, it's probably not okay.
Okay.
Makes sense.
That's what I believe.
Yeah.
Because the speed at which it runs, I doubt that it's every time checking unless you ask
it to do an update.
There's like sync and lock commands versus run and so on.
There's other interesting things we're diving into here.
For example, like the Docker integration.
If you don't even want this thing on your computer, you can actually get a Docker version, run it,
and then just alias commands to your Docker container or things like that.
Or it talks about how to use, how to build it using Docker or like, here you go, for example,
here's how you would get, get it to run, get it to install and run something using a Docker
command and so on.
So there's, there's a lot of things going on, GitHub actions, pre-commits.
This is a super deep project.
If you look at a release, if you look at workspaces, this is a lot of stuff around mono repos.
So if you've got a bunch of different packages and you want them all to be treated as kind
of managed by one, one thing here.
But you can say I have a dependency.
This part of my code has a dependency and another part of my code, please install it as, as you're
running with it or just run it in editable form out of this directory.
A lot of stuff going on here.
I've been checking it out this morning.
So I'm going to let people dive in more for themselves here and maybe listen to the Talk
Python episode from, with Charlie soon.
However, also I want to say thank you to a couple of folks who sent in this.
Skylar, Casco, and John Hagen both said and said, Hey, you guys should check out these
things around this announcement.
One is Simon Wilson, speaking of living in Kansas, no longer lives in Kansas, but part
of the Django team.
He wrote a blog post called UV Unified Python Packaging, huge release from the Astral team
and basically says, this has been out for a couple of hours.
Let me, let me just see what, give you my real quick impressions.
It's kind of a, like a walkthrough almost like here's what I think is important from it.
I think more interesting perhaps is to bump over to Omnivore here and look at what Armin
Roeneker said of creator, original creator of Flask, most recent creator of Rye, R-Y-E,
which has been something kind of trying to do this a little bit, but not as ambitious.
And he handed over ownership of Rye to the Astral folks as well.
So it's kind of, some of this stuff is kind of a blending of these things.
So his article is super interesting.
There's a lot of opinion and takes on it.
Put a few highlights here in Omnivore.
So for example, one of, when creating Rye, he says, one of the things I mentioned there
is that the goal of a packaging tool has to be that will dominate the space.
That is, it's awesome.
If you're not first, you're last.
Not in like a, if you're a second, you're the first loser.
Not in that sense, but in the sense for it like really to make a big impact, it has to be the way,
right?
If there's 20 ways.
This is the way.
Yeah, it's more, more of like the Mandalorian thing.
This is the way.
That's right.
So if it's going to simplify the Python experience, it can't be that there's 20 ways, different
and unrelated ways to simplify.
There has to be a way we kind of agree on, right?
And then it goes on to say-
I don't agree, but that's okay.
Yeah, no, I hear you.
I really want everyone who gets to learn and experience Python, not to remember it as an old
language, bad tooling, but it is an amazing language with stellar, stellar developer,
experience.
Unfortunately, that's not the case today because there are so much choice, so many tools that
are not quite compatible and by the inconsistency everywhere.
That's what he's getting at.
He said, well, I think UV is poised to be this tool.
Now the momentum, now's the moment to step up as a community and start to start to rally
around it.
Yeah.
He needs to take the next step.
Say some of these tools are no longer recommended.
For example, we stopped recommending Easy Install and took them out of our guides.
So I recommend that you consider making UV an option in your documentation.
Also has a little bit of interesting commentary about, well, this is VC funded.
What if they turn evil?
I don't think that they will, but what if they did?
And he talks about that as well.
So-
Yeah.
We can always work it.
Yeah.
Let's see what Henry has to say as well out there.
Says, this is basically mostly faster PIPX replacements.
The script runner, tool management, tool running without installing first.
I agree.
There's, I didn't point it out, but you're right that there's a lot of overlap of PIPX and
this.
Although I think there's more to it as well.
Yeah.
One of the things I'm, I'm interested in is there's, there's been, I've never really,
there's something about the, there's nothing, nothing really against PDM, but my, my experience
with it was just not what, not what I like to do.
And, and UV, the UV tools have taken a lot of the ideas from PDM as well, which is interesting
that they're, they're looking at all, they're taking the inspiration from all over the place.
So they are.
One of the things I don't necessarily like is a lot of it, a lot of it turns the Python package
and sort of environment and project management into UV project and package management.
So for example, you know, you type UVX run or UV, UV add instead of PIP, just pip install,
right?
Where the UV add will put it into the, the lock file and the requirement and so on.
And the lock files even like UV dot lock or something.
Yes.
So I am quite excited about it.
However, a lot of the stuff has, you know, it's kind of founded on virtual environments,
which if you just want to activate the virtual environment and go do your thing, once you,
you maybe get your Python installed if it didn't exist or whatever, then you can go on and do
a lot of things, the, the Python way without worrying about it.
But it's going to be interesting what the adoption is.
I'm going to talk to Charlie soon about it and it'll be fun.
Good.
I'll listen to that one.
Yeah.
I'm super excited about UV in general, so we'll see where it goes.
Yeah.
All right.
I believe that is it for our main items.
Well, based on your, your tab count, I'm guessing that you're feeling pretty extra.
Yeah.
This will go quick though.
I wanted to point out that the, the Jeff triplet rewrite of the top Python packages is, is already
scriptified UV scriptified.
He included the script at the top to pull in the dependencies.
And, you know, once you look at it for something you're, you're, you're familiar with, you're like,
Oh, that's easy.
You're just adding like HTTPX rich and type or to the dependencies and telling which Python version.
That's really all.
That's, I mean, there might be other stuff that you can do, but this is great to be able to just do UV run with this.
I wonder if the editors auto collapse that.
It'd be awesome if you just never see that unless you want to, you know, like it collapses, it folds the code for those sections on open.
Yeah.
Cause if you had like some weird, some weird, corporate thing that you had to stick at the top of your code.
Also, you'd have to scroll down three pages before you get actual.
Yeah.
Um, okay.
So, this is a, like us, owed to Hugo because, or Hugo VK, because, he also, let us know that when we changed the date from Tuesday to Monday, people could use, are we meeting yet.com to keep track of, of when the meeting is because it, it converts to your time, whatever we push this in at.
So I'm seeing that, the next meeting is, is August 26th.
That's today.
Um, so, but if you go here when we're not here, it'll tell you that there's, there's like a meeting coming up and it'll show how many, how many, how much time left.
And there's even a calendar entry that you can add, there.
So that's fun.
And then a link to the, I added the link to the live stream.
So if you click on the live stream link, you can see live stream.
So then that's the real way.
Cause this is, if you do a, are we, are we meeting yet.com?
It doesn't update if we ever have to change things, but yeah, the time is embedded in the URL.
It just adapts to the, that time and the title for your location.
Yeah.
So if you really, want to make sure check out the live stream link.
Okay.
So, and while I was looking at the top, the top PyPI packages, I was looking through, at Hugo VK's, other projects.
And I'm like, oh, there's some cool stuff here that he's published.
So I wanted to shout out to, to a couple of these Python logos from around the world from different Pycons.
So these are fun.
Um, he just has a selection of different ones.
Like, yeah, it's great.
I love these.
That's pretty Pycon Zimbabwe.
That's awesome.
Um, and then also, PyPI downloads.
Um, it's some, some, tools for Python tools with the download counts for versions over time, which is sort of fascinating how slow some stuff like gradually gets down.
So what is, what are we looking at here?
We've got, three, three, 12.
So we've got this, this blue is three, 10, three, 10, 11, 12 is blue is, is up in this top right corner.
And then the old ones like nine, eight, seven, six, five, three, four, are just gradually going down over time.
Um, and it, I kind of would have expected a sharper drop, but, yeah, it's interesting.
And that, that, that sort of trend goes like, here's your URL of three.
Yeah.
Two, six on there for a while.
Yeah.
Well, and two, yeah, two, six did like take a long time to completely disappear.
Two, seven is down into the like single digit percents, but it's not gone away.
Um, so yeah.
Anyway, interesting.
Um, the other thing, he's got, Python, there's a bunch of stuff, Python core devs.
I thought was interesting of different core devs and there when they started and stopped.
So I, I didn't know that people stopped.
I thought we were like core dev for life or something, but, you don't have to be, I guess.
So interesting, graphic.
The other thing I wanted to, the last thing I wanted to extra is that, at, Python
test.com, we've got the courses of course, and they're going, they're going really well.
And I'm excited about that.
The, the other thing we've added is, when I had an, on the other platform, I used to be
on teachable.
Now we're on, Podia.
Um, but Podia has a community thing.
So we've added community options so that if, if you like, for instance, this is great about
the community options, because if you bought the book physical book, but you have a question,
how do you get that answered?
Well, you can hop on and, and join the community here.
So then you can answer, ask questions.
Do you have any extras for us?
Oh, I have many, but I'll make them quick as well.
The Python course for coding in a castle in October 5th to 12th is happening.
And the time is coming up short for if you want to be part of it.
So I would love to spend a week with you in Italy, half programming and half drinking wine
and traveling around.
So if you could, you're interested about in being in that and you're like, Oh, maybe that
would be interesting.
Well, time, the time is now to sign up because, we're going to call it'll be done.
And soon, you know, the, the applications will be closed.
So follow up from last week.
Remember I talked about PI awaitable.
I'd been waiting for it.
So, zero intensity, the author of PI awaitable commented says, Hey, author of PI awaitable here.
Thanks for showcasing.
You were right.
The PEP didn't get published with a number.
I was working with Peter Victorin on it.
And we only got as far as a discussion thread, but unfortunately something that only uses the public API.
Doesn't make a strong proposal.
So the draft got scrapped and turned into documentation.
The plan is to integrate it into CPython sometime in the future, depending on how much maintenance needs, which hopefully should not be that much.
Quoken as a true maintainer right there.
Um, Brian, let's talk web browsers real quick.
So we've got Vivaldi, which is what I'm using.
Obviously Firefox is, well known people use Chrome for some reason still these days.
I don't understand it, but that it still is like, let me run spyware and type into it.
Okay.
Um, there's Safari, there's edge or the bunch of options, right?
Brave.
So on.
But there's this new project that I came across called ladybird, which is pretty interesting.
Interesting here.
Uh, welcome to ladybird.
A truly independent web browser.
We're building a brand new browser from scratch backed by a nonprofit.
That's kind of interesting, isn't it?
Kind of look go scroll to the top again.
Isn't that the, isn't that the meta logo or?
No, it's not meta.
It does look, it does look a little bit like it, but it's, it's not, I think it's supposed to look like a bird with, I don't know.
It's, it's similar, but it's not meta.
Okay.
It's not meta.
So it's an open source and open source project that has six full-time developers working on it and they expect to ship in
2026, which is a lot of work, but you know, web browsers are basically operating systems these days, but it's pretty interesting actually.
So there's a newsletter you can sign up for.
There's an FAQ.
They have sponsors getting, you know, a decent amount of money.
But yeah.
What does it mean?
Where's it come from?
And so on.
So I didn't know.
I just, I ran across that and thought that was interesting.
Yeah.
Jay out there in the audience says, Hey, you're going to buy me a ticket for this, code in the castle.
Yeah.
We'll see.
Wait, you're not buying me a ticket.
Well, get yourself to Germany and then it's, or Austria and it's a short little trip on down.
Okay.
Just across the Alps there.
Okay.
Next one.
Someone asked us about, like, so sorry, I forgot to write down the name when I, I wrote down this note.
It says, Hey, I'm interested in your video.
We talked about, I can't remember what we talked about, but some, maybe the new microphone or something.
I said, Hey, I'm also interested in your video recording setup.
And would that be cool as an extra?
Okay.
So sure.
I'll, I'll give people a rundown on this and Brian, you can chime in on yours.
I record all of the talk Python courses these days with OBS, OBS studio, which is awesome.
It lets you basically record your screen, record your face, set up multiple scenes, do green screens, picture and picture with the background cut out.
So you're just a little bloating human in the bottom of some piece of software.
This is free.
You can download it, runs on all the things.
I encourage people to contribute and donate to it.
Like if you really use this a lot, they have, they have a Patreon thing, so I support them on Patreon.
But this is really nice for recording, setting things up and then controlling it with my steam deck, stream deck rather.
This is a really cool little bit of software that lets you change the lighting, change what's shown, stop, start, pause, et cetera.
Also have, for some reason, the product page for the Elgato key light says that their store is undergoing maintenance, but the rest of the website is up.
So they point over here, so I can show you at least on Amazon.
I've got some cool Elgato key lights that can control with a stream deck and multicolor and stuff.
That's really fun.
And then finally, edit all of this with DaVinci Resolve.
DaVinci Resolve is super fun software.
They use it for a lot of the Marvel movies, I believe.
They use it for Spider-Man.
So it's kind of intense.
If you open it up, you're like, what am I supposed to do with this?
But if you just stay in the little edit section with the timeline, then it's pretty manageable and pretty nice to use.
So that's also free.
So that's what I'm doing these days.
Cool.
Yeah.
I'm doing a lot of that.
I want to switch to, I want to try the open.
OBS.
I'm currently using Camtasia for recording stuff.
Not for this show, but for courses and stuff.
I use Camtasia.
And Camtasia is oddly, it works better on Windows than it does on Mac.
Because you can export multiple.
It's actually something I'm looking for on a Mac.
I want to be able to record everything in one project and then export multiple videos from one project.
And you can't do that with Camtasia.
I don't think you can do that with that other.
DaVinci.
But maybe you can.
I just don't know how.
Yeah.
I have maybe 100 videos for some courses and they're all in one project in DaVinci.
It's pretty nice.
Also, I'm using Stream Deck.
I love Stream Deck.
And the key lights.
They're great.
The one thing that you didn't mention was what camera you're using.
Oh, yeah.
I'm using.
I've used a whole bunch.
So this is not a strong recommendation.
But I'm using the Elgato.
She can't look like that thing.
The Elgato.
What is it called?
Facecam Pro.
That's what it's called.
Okay.
Which is like a 4K camera.
That's pretty good.
Yeah.
It's pretty good.
Yeah.
It's pretty good.
The color is a little bit off.
Like, it's hard to get just real natural colors.
I'm using the Logitech Logi.
A little tiny camera.
Which is decent.
I think I used that before.
And it's also real nice.
Yeah.
But it'd be fun if I tried this other one.
And also so that we looked a little more similar.
I'm usually showing up lighter than you.
Might be a lighting thing.
But anyway.
Yeah.
For sure.
Let's see.
Also, just to round this out.
For the live streams, we use StreamYard.
Oh, yeah.
We've been happy with that.
Yeah.
StreamYard is really good.
Really good.
And Jay Miller out there says,
If you're doing both recording and streaming,
I recommend Ecamm.
Massive fan.
They built Zoom stream support,
which is, yeah.
Jay does some cool live streaming as well.
So, all right.
That was actually kind of a long-winded answer.
But that's what we're doing, folks.
For those of you who aren't interested.
Yeah.
Anything else?
Are we up to the joke?
I am ready to tell the joke.
And now, this joke has no graphic.
No graphic.
But I thought I would put,
just for the live stream here,
I would put a picture of a really nice data center
so people can appreciate their code running
in like an awesome place here.
Okay?
Yeah.
It's terrible.
Okay.
It's that.
It's a really bad,
a really bad looking place there.
So, here's the joke.
This is like an Alcoholics Anonymous meeting type of thing.
Okay.
Which, alcoholism is not funny,
but making fun of DevOps is.
So, let's do it in that style, right?
This joke is adapted from a joke Blaze wrote and sent in.
So, this is the DevOps support group.
Are you ready, Brian?
Yeah.
Hi.
My name is Bob.
Group.
Hi, Bob.
It's been 42 days since I last SSH'd into production.
Applause for the group.
But only four days since I actually took down the website.
Someone in the back.
Oh, Bob.
That's funny.
Yeah.
It's a good one.
Yeah.
You don't want to be the one who took down the website.
How?
If he didn't SSH into production.
Well, he must have shipped a bad Ansible script or something.
I don't know.
Yeah.
Like, I knew the last time I took down the website inadvertent, I was completely out of
the blue.
I'm like, what in the world is happening?
Was I was using the Walrus operator.
And Python, it was a while ago, Python 3.7 was running on the server.
I didn't use the Walrus operator on the website code.
I used it on a, like, utility thing.
But the script was collected in a subsection where the web framework scanned for routes for
the framework.
And as it tried to parse the Walrus code to see if it could add it to the website, it
took down the website instead.
It couldn't start.
Oh, no.
Yeah.
Anyway.
Oh, Bob.
Don't be Bob.
Stay on top of stuff with Python bytes.
Get all the latest things.
Don't be Bob.
Unless your name is Bob.
Then you be Bob.
Don't be that Bob.
Exactly.
All right.
Well, thank you, everyone, for being here and sending in all the stuff.
a lot of fun Brian
see you later
thanks a lot bye