Topics covered in this episode:
Watch on YouTubeAbout 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 11am 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: Better Django management commands with django-click and django-typer
Michael #2: PSF Lands a $1.5 million sponsorship from Anthropic
- Anthropic is partnering with the Python Software Foundation in a landmark funding commitment to support both security initiatives and the PSF's core work.
- The funds will enable new automated tools for proactively reviewing all packages uploaded to PyPI, moving beyond the current reactive-only review process.
- The PSF plans to build a new dataset of known malware for capability analysis
- The investment will sustain programs like the Developer in Residence initiative, community grants, and infrastructure like PyPI.
Brian #3: How uv got so fast
- Andrew Nesbitt
- It’s not just be cause “it’s written in Rust”.
- Recent-ish standards, PEPs 518 (2016), 517 (2017), 621 (2020), and 658 (2022) made many
uv design decisions possible - And
uv drops many backwards compatible decisions kept by pip. - Dropping functionality speeds things up.
- “Speed comes from elimination. Every code path you don’t have is a code path you don’t wait for.”
- Some of what uv does could be implemented in pip. Some cannot.
- Andrew discusses different speedups, why they could be done in Python also, or why they cannot.
- I read this article out of interest. But it gives me lots of ideas for tools that could be written faster just with Python by making design and support decisions that eliminate whole workflows.
Michael #4: PyView Web Framework
Extras
Brian:
- Upgrade Django, has a great discussion of how to upgrade version by version and why you might want to do that instead of just jumping ahead to the latest version. And also who might want to save time by leapfrogging
- Also has all the versions and dates of release and end of support.
- The Lean TDD book 1st draft is done.
- Now available through both pythontest and LeanPub
- I set it as 80% done because of future drafts planned.
- I’m working through a few submitted suggestions. Not much feedback, so the 2nd pass might be fast and mostly my own modifications. It’s possible.
- I’m re-reading it myself and already am disappointed with page 1 of the introduction. I gotta make it pop more. I’ll work on that.
- Trying to decide how many suggestions around using AI I should include.
- It’s not mentioned in the book yet, but I think I need to incorporate some discussion around it.
Michael:
Joke: Reverse Superman
