Tall, Snarky Canadian

While writing the section of my 2026 Python Packaging Council (PPC) nomination on secure supply chain, I realized that one thing related to having a secure supply chain that we lack is a defined way to perform reproducible builds.

I have decided to run for the inaugural/2026 Python packaging council (PPC).

There have been several security incidents lately that involved compromising GitHub Actions workflows.

While I decide what to do with PEP 832 after polling folks on their opinion, I thought I would write out why I'm even bothering with any of this.

A Python project got hacked where malicious releases were directly uploaded to PyPI.

It's been a while since I posted about WASI support in CPython!

In case you didn't hear, PEP 810 got accepted which means Python 3.15 is going to support lazy imports!

I want to be upfront that this blog post is for me to write down some thoughts that I have on the idea of rewriting the Python Launcher for Unix from Rust to pure Python.

I was writing some code where I was using httpx.get() and its params parameter.

(This is the blog post version of my keynote from EuroPython 2025 in Prague, Czechia.)

PEP 750 introduced t-strings for Python 3.14.

I normally don't talk about politics here, but as I write this the US has started a trade war with Canada (which is partially paused for a month, but that doesn't remove the threat).

When I was about to go on paternity leave, the Gleam programming language reached 1.0.

In the past week I had two people separately tell me what they thought the Python Software Foundation Conduct WG did and both were wrong (and incidentally in the same way).

In my opinion, you should only introduce a named tuple to your code when you're updating a preexisting API that was already returning a tuple or you are wrapping a tuple return value from another API.