Topics covered in this episode:

About the show

Sponsored by us! Support our work through:

Connect with the hosts

Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 10am PT. Older video versions available there too.

Seth Larson
It seems like security is special in a sense that we don’t want just anyone working on the security aspect of a project. We just want the trusted maintainers, right?
Seth is arguing that this is the wrong mindset
It makes more sense that we maybe have security experts contribute to many projects, and that someone working on security for just one project doesn’t benefit from scale.
- “Maintainers don’t see how other projects are triaging vulnerabilities and can’t learn from each other. They can’t compare notes on what they are seeing and whether they are doing the right thing. Isolation in security work breeds a culture of fear. Fear of doing the wrong thing and making your users unsafe.”
- “These “security contributors” could be maintainers or contributors of other open source projects that know about security, they could be foundations offering up resources to their ecosystem, or engineers at companies helping their dependency graph.”
But how do we build trust in these individuals?
- Meeting in person works.
- But there are other ways as well.
I’d personally love to have someone contact me about a project of mine regarding a security problem or process that the project could/should follow. Especially if I could see other projects I trust already trusting this individual to work on the other projects.

Michael #2: uv v0.8

Brian #3: Extra, Extra, Extra

Michael #4: Announcing Toad - a universal UI for agentic coding in the terminal

And … Cloud Architects 2025 “They send us our cloud bills in scientific notation… “ 🙂

#442 Cloud bills in scientific notation

Python Bytes