Python Bytes

#504 Who turned the GIL back on?

Nov 10, 2026
PyPI adds provenance warnings and attestations to help spot compromised releases. GILguard tracks imports that quietly re-enable Python’s GIL, while pip 26.3 tightens wheel safety and introduces pylock extras. Also featured: a virtual refrigeration honeypot, AI-assisted supply-chain checks, expanded Python security support, and a treasure trove of developer utilities.
Ask episode
AI Snips
Chapters
Transcript
Episode notes
INSIGHT

PyPI Makes Provenance Changes Visible

  • PyPI’s redesigned project pages make package provenance visible through a Security tab and per-file attestations.
  • “No provenance” means unverifiable origin, while incomplete, inconsistent, changed, or lost provenance can signal a compromised publishing pipeline.
ADVICE

Verify Unexpected Package Provenance Changes

  • Treat provenance changes or unexpected losses skeptically and verify them with maintainers before trusting a release.
  • PyPI specifically warns that changed provenance can indicate an account takeover or compromised build pipeline.
INSIGHT

Unsupported Extensions Can Undo Free Threading

  • Free-threaded Python can silently reactivate the GIL when importing an unsupported native extension, permanently collapsing parallelism.
  • The resulting contention may perform worse than ordinary single-threaded execution, making benchmarks especially misleading.
Get the Snipd Podcast app to discover more snips from this episode
Get the app