#442 Cloud bills in scientific notation
Python Bytes
Intro
This chapter explores the intricacies of security in open source projects, addressing the importance of professional expertise and community collaboration. It discusses strategies for building trust among contributors to enhance security practices within the Python community.
- * Open Source Security work isn't “Special”*
- * uv v0.8*
- * Extra, Extra, Extra*
- Announcing Toad - a universal UI for agentic coding in the terminal
- Extras
- Joke
About the show
Sponsored by us! Support our work through:
Connect with the hosts
- Michael: @mkennedy@fosstodon.org / @mkennedy.codes (bsky)
- Brian: @brianokken@fosstodon.org / @brianokken.bsky.social
- Show: @pythonbytes@fosstodon.org / @pythonbytes.fm (bsky)
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.
Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it.
Brian #1: Open Source Security work isn't “Special”
- 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
- Changes
- Install Python executables into a directory on the
PATH - Register Python versions with the Windows Registry
- Prompt before removing an existing directory in uv venv
- Bump --python-platform linux to manylinux_2_28
- Make uv_build the default build backend in uv init
- And many more
- Install Python executables into a directory on the
- And uv v0.8.1
- And uv v0.8.2
- And uv v0.8.3
- Adds Add CPython 3.14.0rc1
Brian #3: Extra, Extra, Extra
- fstrings.wtf - Armin Ronacher
- Python 3.14 release candidate 1 is go!
- Django turns 20, with parties
- mkdocs-redirects
- I’m Tired of Talking About AI - Paddy Carver
Michael #4: Announcing Toad - a universal UI for agentic coding in the terminal
- by Will McGugan
- A universal front-end for AI in the terminal.
- Watch the video.
Joke: Heaviest objects in the universe
And … Cloud Architects 2025 “They send us our cloud bills in scientific notation… “ 🙂
The AI-powered Podcast Player
