Saltar al contenido
PodcastsNoticiasPython Bytes

Python Bytes

Michael Kennedy and Calvin Hendryx-Parker
Python Bytes
Último episodio

490 episodios

  • Python Bytes

    #489 Or JSON?

    21/07/2026 | 30 min
    Topics covered in this episode:

    django-orjson

    Best Django Redis configuration for speed and size

    Linus Torvalds puts the foot down against Anti-AI Kernel Maintainers

    Django Steering Council backs the Triptych Project

    Extras

    Joke

    Watch on YouTube

    About the show

    Sponsored by us! Support our work through:

    Our courses at Talk Python

    Consulting from Six Feet Up

    Connect with the hosts

    Michael: Mastodon / BlueSky / X / LinkedIn

    Calvin: Mastodon / BlueSky / X / LinkedIn

    Show: Mastodon / BlueSky / X

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

    Michael #1: django-orjson

    Adam Johnson dropped django-orjson - drop-in replacements for the Django and DRF pieces that touch JSON, swapping stdlib json for orjson, the Rust-based library. Headline numbers: 10x faster serialization, 2x faster deserialization.

    The interesting question is why this needs to be a package at all. pip install orjson is the easy part. Adam's actual pitch: adopting it "isn't easy, especially when your framework uses json in many different parts." Django scatters JSON across JsonResponse, the test client and test case classes, the json_script template tag, and more. There's no single hook to grab, so you get a library that catches them all.

    Adam is refreshingly honest about the scale of the win. His words: "While database queries tend to dominate the typical Django application's runtime, the time spent in serialization and deserialization can still be significant." He calls it "a nearly free performance win" - not "this will 10x your app." That's a claim about cost, not magnitude, and it's worth keeping those straight.

    Worth flagging what the post doesn't cover: caveats. There are none in the article, but orjson has real ones. Django and Flask both render datetimes as RFC 822 HTTP-date (Wed, 15 Jul 2026 12:00:00 GMT); orjson does ISO 8601. It can't do ensure_ascii, it rejects NaN and Infinity (which stdlib happily emits), and it raises on Decimal. If you've got a JS client parsing dates, that's a wire-format change.

    Who should actually take this? If you're a DRF shop shoveling JSON all day, yes - it's cheap and it's real. If your app mostly renders HTML templates, you're optimizing a slice of runtime that's already near zero.

    The problem Adam's package solves doesn't exist in Flask or Quart. They already centralize every JSON operation - jsonify, request.get_json(), the test client, the |tojson filter - behind one provider object at app.json. So there's no library to install. It's about ten lines:

    import orjson
    from quart.json.provider import JSONProvider # or flask.json.provider
    class OrjsonProvider(JSONProvider):
    def dumps(self, obj, **kwargs) -> str:
    return orjson.dumps(obj).decode() # provider must return str
    def loads(self, s, **kwargs):
    return orjson.loads(s)
    app.json = OrjsonProvider(app)

    The numbers on talkpython.fm

    Evaluated it, measured it, and skipped it. The biggest JSON payload we serve is our MCP server returning a cached episode transcript, about 139 KB. Swapping the provider saves 0.119 milliseconds per request. That total response takes 1.1 ms

    We got 4.1x, not 10x - and the reason is the good lesson. Payload shape decides your speedup. The 10x is for structure-heavy data, lots of small keys where stdlib burns time in Python-level dispatch per item. Our hot payload is one giant transcript string, so the work is escaping and memcpy

    Calvin #2: Best Django Redis configuration for speed and size

    Peter Bengtsson revisits a classic: his 2017 "Fastest Redis configuration for Django" benchmark now has a 2026 update posted this week.

    The 2017 post pitted django-redis serializers (json, ujson, msgpack, pickle) and compressors (zlib, lzma) against each other; conclusion was msgpack + zlib as the sweet spot - avoid the json serializer, it's fat and slow.

    The 2026 update narrows focus to just compressors: default (no compression), zlib, lzma, and newcomer zstd.

    New results: lzma compresses best but is slowest; zstd is the fastest compressor on Ubuntu; differences between them are very small.

    Big takeaway across both: compression buys you a lot of space (2–3.5x smaller) for very little speed cost - worth it for Redis where memory is the constraint.

    Caveat from the author: results depend heavily on your data - his test stores short strings of numbers, so benchmark your own workload.

    Michael #3: Linus Torvalds puts the foot down against Anti-AI Kernel Maintainers

    Write up on Ars.

    Really good coverage by Maximillian: Time to wake up (for some)

    Torvalds said that “Linux is not one of those anti-AI projects, and if somebody has issues with that, they can do the open-source thing and fork it. Or just walk away.”

    I agree with Max, putting your head in the sand and waiting for AI to go away will likely mean you won’t be working professionally in software development in the coming years.

    The statement came amid a lengthy thread arguing about the use of Sashiko, an “agentic Linux kernel code review system” that its creators claim can, in tests, independently find 53.6 percent of the bugs that would end up being fixed by human coders in later commits.

    “We’re not forcing anybody to use [LLM tools], but I will very loudly ignore people who try to argue against other people from using it,” Torvalds said.

    “Anybody who points to the problems at AI had better be looking in the mirror and pointing at themselves at the same time,” Torvalds wrote.

    Calvin #4: Django Steering Council backs the Triptych Project

    Django Steering Council issued a Letter of Collaboration backing Carson Gross & Alex Petros's funding bid for the Triptych Project - three proposals to make HTML more expressive natively, in every browser.

    The three additions: PUT/PATCH/DELETE methods for forms, button actions (buttons that fire HTTP requests without a wrapping form), and partial page replacement.

    Distills the core ideas from HTMX/Unpoly/Turbo into the HTML standard itself - no JS, no library, nothing to ship or maintain.

    Current focus is button actions (WHATWG #12330): <button action=/logout method=POST>Logout</button> instead of wrapping a button in a form.

    Relevant to Django directly - think the admin submit row and disguised delete links; Django 6.0's template partials were already inspired by these patterns.

    How to help: companies can send non-binding letters of support on letterhead; individuals can read the proposals and weigh in on the WHATWG issues.

    Extras

    Calvin:

    DOOMQL - A playable first-person shooter whose framebuffer is a SQL query.

    Michael:

    Granian 2.7.9 fixes WSGI threadpool scheduler starvation/underscaling

    Welcome Calvin post

    Joke: Solving all bugs
  • Python Bytes

    #488 tau - it's 2pi and it writes code

    14/07/2026 | 32 min
    Topics covered in this episode:

    The trusted-publishing debate: how to do it right vs. why you shouldn't trust it

    JupyterLab 4.6 and Notebook 7.6 are out!

    Tau – new small, readable terminal coding agent

    Django Tasks and Django 6.1

    Extras

    Joke

    Watch on YouTube

    About the show

    Sponsored by us! Support our work through:

    Our courses at Talk Python

    Consulting from Six Feet Up

    Connect with the hosts

    Michael: Mastodon / BlueSky / X / LinkedIn

    Calvin: Mastodon / BlueSky / X / LinkedIn

    Show: Mastodon / BlueSky / X

    Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesday at 7am 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.

    Calvin #1: The trusted-publishing debate: how to do it right vs. why you shouldn't trust it

    https://snarky.ca/how-to-publish-to-pypi-using-github-actions-securely/ (Brett Cannon) and https://blog.yossarian.net/2026/07/07/You-shouldnt-trust-trusted-publishing (William Woodruff)

    Trusted Publishing (PyPI's OIDC-based auth scheme, also now used by npm, RubyGems, crates.io, NuGet) replaces long-lived API tokens with short-lived, auto-scoped credentials tied to CI/CD machine identity.

    Yossarian's post: it's purely an authentication mechanism between a machine identity and a package — it says nothing about package safety or quality. PyPI deliberately avoids any "verified/trusted" badge for it, unlike its verified-URL checkmarks.

    Same logic applies to PyPI attestations: anyone can sign with any machine identity they control, so an attestation's presence isn't itself a trust signal.

    Bottom line from that post: don't confuse "trusted" (machine-to-machine) with "trustworthy" (human judgment about the package).

    Snarky.ca's companion piece is more practical: given GitHub Actions compromises in the news, the real fix is 3 concrete steps — run zizmor to lock down workflow permissions/checkout credentials and pin actions to commit hashes, adopt Trusted Publishing to eliminate stored PyPI tokens, and require manual approval via a GitHub environment before any publish job runs.

    Takeaway for listeners: Trusted Publishing is good hygiene for how you authenticate to PyPI, but it's not a substitute for securing your CI pipeline itself — or for actually vetting the packages you install.

    Michael #2: JupyterLab 4.6 and Notebook 7.6 are out!

    Michał Krassowski's rundown - a chunky minor release: 68 features, 97 bug fixes, 95 contributors, one of the biggest ever.

    Scratchpad console (Notebook 7.6 headliner) - a console next to your notebook sharing its kernel, for throwaway experiments. Ctrl+B.

    Jump to last-edited cell - new commands hop through recently edited cells.

    File browser glow-up - Date Created column, editable breadcrumbs with Tab-completion, and Open in Terminal.

    Debugger - sources open in the main area, floating step/continue overlay, live kernel-sources filter.

    Custom layouts (Lab) - activity bar top/bottom, draggable panels, four-way tab splits, per-panel Ctrl+scroll zoom.

    ~5x faster extension builds - webpack → Rspack, and jupyter-builder means no full Lab install needed to build extensions.

    Keyboard/a11y - add shortcuts from the UI (no JSON), Find & Replace in Edit menu (Ctrl+H).

    Calvin #3: Tau – new small, readable terminal coding agent

    Tau – new small, readable terminal coding agent (Python 3.12+), built as both a working tool and a teaching project for how coding agents work under the hood

    Install via uv tool install tau-ai, pipx, or pip; ships a tau CLI

    Three-layer architecture: tau_ai (provider-neutral model layer) → tau_agent (reusable "brain": messages, tools, events, loop) → tau_coding (CLI/TUI, file & shell tools, sessions)

    Supports OpenAI, Anthropic, OpenAI Codex, OpenRouter, Hugging Face, and custom/local OpenAI-compatible endpoints

    Built-in tools (read/write/edit/bash), durable JSONL sessions with resume/branching, project instructions via AGENTS.md, and context compaction

    Core harness is UI-agnostic — same brain can power the TUI, print mode, or a custom frontend — usable as a standalone library too

    Michael #4: Django Tasks and Django 6.1

    Django 6.0 finally ships first-party background tasks (django.tasks) - out of Jake Howard's DEP 14, accepted May 2024, after two decades of everyone bolting on Celery/RQ/Huey.

    It's an API, not a worker. Django handles task definition, validation, queuing, and result storage - it does not execute them. You bring the backend.

    The default backend traps people. ImmediateBackend runs tasks inline on the request thread and blocks until done - so out of the box .enqueue() backgrounds nothing (a 5-second task means a 5-second response). The other built-in, DummyBackend, runs nothing at all. Both are dev/test only.

    Nice API otherwise: slap @task on a function, call .enqueue(), get back a TaskResult you look up later by id - with async twins like aenqueue(). Gotcha: args and return values must survive a JSON round-trip, so a tuple sneakily comes back as a list.

    The community local backend to know: django-tasks-local by Chris Beaven (SmileyChris). A ThreadPoolExecutor backend that gives real background threads with zero infrastructure - no Redis, no Celery, no database - plus a ProcessPoolBackend for CPU-bound work → github.com/lincolnloop/django-tasks-local

    Its catch: results live in memory, so pending tasks vanish on restart or deploy. Great for dev and low-traffic production; for persistence, drop to Jake Howard's django-tasks (DatabaseBackend + worker command).

    Extras

    Calvin:

    Fixing the dictionary with Python 3.14 — Hugo van Kemenade stumbled on - and got fixed - a markup bug in the OED's own citation of a 1706 use of the pi symbol.

    Michael:

    Bunny DNS is now free

    Jokes:

    What's the object-oriented way to become wealthy? Inheritance

    To understand what recursion is... You must first understand what recursion is

    3 SQL statements walk into a NoSQL bar. Soon, they walk out They couldn't find a table.
  • Python Bytes

    #487 Minimum requirements

    07/07/2026 | 27 min
    Topics covered in this episode:

    dust - a better du

    Hermes Agent: The AI agent that grows with you

    llm-coding-agent 0.1a0

    Extras

    Joke

    Watch on YouTube

    About the show

    Sponsored by us! Support our work through:

    Our courses at Talk Python

    Consulting from Six Feet Up

    Connect with the hosts

    Michael: Mastodon / BlueSky / X / LinkedIn

    Calvin: Mastodon / BlueSky / X / LinkedIn

    Show: Mastodon / BlueSky / X

    Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesday at 7am 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.

    Michael #1: dust - a better du

    du + Rust = dust - a fast, visual, intuitive disk-usage CLI

    Run dust and immediately see the biggest directories and files without piping through sort, head, or awk

    Smart recursive output focuses on what matters instead of dumping every folder

    Colored bars show relative size and parent/child hierarchy, making “where did the space go?” obvious

    Perfect for Python projects bloated by .venv, caches, Docker volumes, downloaded datasets, and local AI models

    Install via brew, cargo install du-dust, conda-forge, Scoop, Snap, deb-get, or GitHub releases

    Calvin #2: A Way better ARchive format for Python packaging

    war - new archive format spec from Astral (same team as uv/ruff), v0.0.2, still no binary encoding defined yet

    Header-Index-Store layout: header IDs the file, index maps names to store offsets, store holds compressed data

    Index uses a finite-state transducer (FST) to dedupe common path prefixes across entry names

    Supports three entry types (file, directory, link) and three compression modes (store/DEFLATE/zstd), plus an "executable" metadata flag

    Unpacking is atomic - writes to a temp dir, then renames into place, so a failed extract never leaves a half-unpacked directory

    Strict name-segment rules (no NUL/control chars, no leading/trailing whitespace, blocks Windows-reserved names like CON/PRN) to avoid path traversal and cross-platform footguns

    Michael #3: Hermes Agent: The AI agent that grows with you

    Hermes Agent is an open-source, Python-built AI agent framework from Nous Research - think ChatGPT-style assistant, but connected to your tools, files, shell, browser, calendar, memory, and messaging apps

    I’m using it in Discord as a long-running agent conversation, not just a one-off chatbot session

    Hermes can connect through a gateway to platforms like Discord, Telegram, Slack, WhatsApp, email, webhooks, and more - so the same assistant can follow you across surfaces

    In my setup, I can send Hermes voice/text from Discord, keep project context across turns as threads, and ask it to actually do things: read GitHub repos, run commands, edit files, schedule calendar events, generate drafts, and verify results

    A fun workflow: I can trigger one-shot actions from an Apple Watch shortcut - dictate a request, send it to Hermes, and have the agent execute it asynchronously

    Hermes has persistent memory, so it can remember durable preferences and facts - for example, how I like my research formatted

    It also has “skills,” which are reusable procedures the agent can load later, so Hermes can self-improve over time instead of rediscovering the same workflow repeatedly

    It supports scheduled jobs / cron-style automations, so it can proactively watch for releases, send summaries, run checks, or remind you about things

    It’s provider-agnostic: OpenRouter, Anthropic, Google, xAI, local models, Nous Portal, and others

    The big idea: Hermes turns an LLM from “a chat box I visit” into “an agent I can reach from anywhere that knows my workflows and can take real actions and learns over time.”

    Calvin #4: llm-coding-agent 0.1a0

    Simon Willison built a Claude/Codex-style coding agent on top of his llm library, using an alpha of the llm package plus his python-lib-template-repo

    Built almost entirely via prompted TDD - asked an agent to write a spec.md, then commit + implement with red/green tests, occasionally hitting a real OpenAI key to sanity-check

    Shipped to PyPI as an alpha: uvx --prerelease=allow --with llm-coding-agent llm code

    Tool set mirrors familiar coding-agent primitives: read_file, edit_file (exact string replace + diff), write_file, list_files, search_files, execute_command

    Also exposes a Python API - CodingAgent(model="gpt-5.5", root=..., approve=True).run(...) - which Simon didn't ask for but got anyway

    Demo: llm code --yolo told GPT-5.5 to build a SwiftUI CLI clock; model correctly noted SwiftUI isn't really CLI-friendly and still produced an ASCII-art time display

    Extras

    Calvin:

    Slides, but for developers https://sli.dev/

    Wanna reduce your token usage…. only issue is that its lossy https://github.com/teamchong/pxpipe

    PEP 772 - Python Packaging Council inaugural election dates set, nominations open July 28, voting September 1-15

    Michael:

    What the pls? revisited!

    Joke: Min requirements for Linux
  • Python Bytes

    #486 underscore-underscore-ghost-emoji

    30/06/2026 | 29 min
    Topics covered in this episode:

    Free-threaded Python: past, present, and future

    django-admin-site-search

    Qwen 3.6 27B is the sweet spot for local development

    A large batch of PEPs are finalized

    Extras

    Joke

    Watch on YouTube

    Show Intro

    Sponsored by us! Support our work through:

    Our courses at Talk Python

    Consulting from Six Feet Up

    Connect with the hosts

    Michael: Mastodon / BlueSky / X / LinkedIn

    Calvin: Mastodon / BlueSky / X / LinkedIn

    Show: Mastodon / BlueSky / X

    Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesday at 7am 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.

    Calvin #1: Free-threaded Python: past, present, and future

    The GIL has prevented true multi-threaded parallelism in CPython since the beginning — multiple past attempts to remove it failed on performance grounds

    Sam Gross at Meta finally solved it; his work became PEP 703 and ships as free-threaded CPython today

    Python 3.13 was experimental with 20–40% single-threaded slowdown; 3.14 brought that to 0–10%

    Python 3.15 (October 2026) delivers a unified ABI — one extension binary works on both GIL and free-threaded builds

    Already >50% of the top PyPI binary wheels support free threading

    Wouters predicts free-threaded becomes the default between 3.16–3.20 (2027–2031), with the GIL eventually disappearing next decade

    Michael #2: django-admin-site-search

    via Adam Parkin

    A global/site search modal for the Django admin, by Ahmed Aljawahiry. Hit cmd+k anywhere in the admin and you get a command-palette-style search window, kind of like the one in VS Code.

    It doesn't just search one model's list page. It searches your entire site in one box:

    App labels

    Model labels and field attributes

    Actual model instances (your data)

    Two ways to search the instances:

    model_char_fields (the default): runs an __icontains across every CharField (and subclasses) on the model. Zero config, works out of the box.

    admin_search_fields: defers to each ModelAdmin's existing get_search_results(), so it respects the search_fields you've already set up.

    The part I like: it's permission-aware out of the box. Users only see results for the apps and models they actually have view permission on, so you're not leaking anything through search.

    Results appear as you type, with throttling/debouncing so you're not hammering the server on every keystroke, and it's full keyboard nav: cmd+k to open, up/down to move, enter to go.

    It's responsive, does dark and light mode, and it pulls Django's built-in admin CSS variables so it just matches whatever admin theme you're running.

    Under the hood it's Alpine.js, but bundled into static so there's no external CDN dependency.

    Setup is about what you'd expect: pip install django-admin-site-search, add it to INSTALLED_APPS, mix the AdminSiteSearchView into your AdminSite, and drop a few template includes into base_site.html.

    Supports Python 3.8 through 3.14 and Django 3.2 through 6.0, MIT licensed, and everything is overridable if you want to skip certain models, add TextField matching, etc.

    Calvin #3: Qwen 3.6 27B is the sweet spot for local development

    Qwen 3.6 27B is being called the first local model that genuinely competes as a general-purpose intelligence — benchmarks put it at roughly mid-2025 frontier level (comparable to GPT-5 / Claude Sonnet 4.5)

    Runs locally via llama.cpp; on an M5 MacBook Max with 8-bit quantization + multi-token prediction, it hits ~32 tokens/sec using ~42GB RAM

    4-bit quantization gets it under 18GB, runnable on 32GB devices; Nvidia RTX cards run it even faster

    The dense 27B is recommended over the faster MoE 35B A3B — author prefers higher quality output over raw speed

    Privacy and reliability are the pitch: fine-tunable, can't be taken down, suitable for sensitive/proprietary data

    Author sees this as a stepping stone — frontier open-weight models like GLM 5.2 are now locally runnable with company-grade hardware, and smarter-still local models are coming

    Michael #4: A large batch of PEPs are finalized

    A bunch of PEPs went from accepted to final.

    668, 687, 691, 699, 701, 703, 728, 770, 773, 829

    But this wasn’t them making their way into CPython. It’s an admin sorta thing. (Thanks PyCoders)

    See the commit.

    Extras

    Calvin:

    More fun bling for your terminal this time - https://charm.land/

    Michael:

    Follow up from pls, What the pls? Thanks Pito.

    Joke: BEMoji

    A production-grade utility and component framework built entirely on emoji class names

    via Jeff Triplett
  • Python Bytes

    #485 Creating memories

    23/06/2026 | 38 min
    Topics covered in this episode:

    Backup Docker volumes locally or to any S3

    Pyodide 314.0 Release

    nb-cli: A Command-Line Interface for AI Agents and Notebook Automation

    Hindsight Agent Memory That Learns

    Extras

    Joke

    Watch on YouTube

    About the show

    Sponsored by us! Support our work through:

    Our courses at Talk Python

    AWS Community Day Midwest tomorrow Wednesday the 24th in downtown Indianapolis, Six Feet Up is sponsoring and there are 2 Sixies presenting

    Connect with the hosts

    Michael: Mastodon / BlueSky / X / LinkedIn

    Calvin: Mastodon / BlueSky / X / LinkedIn

    Show: Mastodon / BlueSky / X

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

    Finally, if you want an bonus 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.

    Michael #1: Backup Docker volumes locally or to any S3

    Via Bryan Weber (thanks Bryan!), who spotted it over on Virtualization HowTo. Find Bryan at bryanwweber.com.

    offen/docker-volume-backup is a lightweight companion container that backs up the volumes your apps actually depend on, then ships them somewhere safe.

    It's tiny: written in Go and about 25MB compressed, roughly 1/20th the size of the shell-based image (jareware/docker-volume-backup) that inspired it.

    Drop it into your docker compose file as a backup service, mount the volumes you care about as read-only, and you're off.

    Push backups to a pile of destinations: a local directory, plus any S3, WebDAV, Azure Blob Storage, Dropbox, Google Drive, or SSH-compatible target. Mix and match as many as you want in one run.

    Recurring cron-style backups in a Compose setup, or one-off backups straight from the Docker CLI.

    Production-friendly touches worth calling out:

    Rotates away old backups so you don't quietly fill the disk.

    GPG encryption for your archives.

    Notifications on finished and failed runs (so you find out about failures before you need the backup).

    Stop a container during backup for a consistent snapshot using a simple docker-volume-backup.stop-during-backup=true label, then auto-restart it.

    Run custom commands during the backup lifecycle (great for a database dump before the file copy).

    Docker Swarm support, plus arm64 and arm/v7 builds. Hello, Raspberry Pi homelab.

    Fun aside from Bryan: he searched our back catalog for this tool and the search came back so fast he thought it hadn't run. Love to hear it.

    Calvin #2: Pyodide 314.0 Release

    PEP 783 is the real news — Pyodide maintainers used to hand-build 300+ packages. Now anyone can publish Pyodide wheels to PyPI with cibuildwheel.

    The version jump from 0.29 to 314.0 is intentional — it now tracks the Python version, so 314.x = Python 3.14. Binary compatibility is locked per Python cycle, meaning packages you build today won't break on the next Pyodide release.

    sqlite3, ssl, and lzma are back in the default stdlib — no more await pyodide.loadPackage("sqlite3"). Bigger download, but a much smoother experience for newcomers.

    bigint precision bug is fixed — values above 2^53 were silently losing precision when crossing the Python/JS boundary. The new JsBigInt type makes the roundtrip correct. Worth flagging if anyone is doing numeric work in a browser app.

    Experimental TCP sockets in Node.js — you can now connect Pyodide to a real database (MySQL, PostgreSQL, Redis tested) when running server-side. Blurs the line between "Python in the browser" and "Python runtime anywhere Wasm runs."

    Michael #3: nb-cli: A Command-Line Interface for AI Agents and Notebook Automation

    From Piyush Jain (Jupyter and LangChain maintainer) on the Jupyter blog: nb-cli: A Command-Line Interface for AI Agents and Notebook Automation.

    nb-cli is an experimental, Rust-based CLI to read, write, execute, and search Jupyter notebooks. The premise: agents are great at CLIs but terrible at hand-editing the nested JSON in an .ipynb, so let them operate on the notebook from the outside instead of running inside it.

    Works with or without a Jupyter server. No server? It reads/writes .ipynb files directly and talks to kernels over ZeroMQ. Connected to a live JupyterLab, your edits show up instantly via Y.js (the same CRDT Jupyter uses).

    Smart output format: instead of token-heavy JSON or ambiguous plain markdown, it uses @@cell / @@output sentinels with inline metadata. Less wasted context, unambiguous structure, and it degrades gracefully on truncation.

    The payoff is composability. "Add a summary section and run it" becomes one shell pipeline instead of six agent tool calls. And nb search notebook.ipynb --with-errors returns only the failing cells, so the agent skips the cells that worked.

    Claude Code tie-in: it ships as an agent skill. npx skills install jupyter-ai-contrib/nb-cli and your agent can drive notebooks via nb.

    Out of jupyter-ai-contrib, which aims to become an official Jupyter AI subproject. Still early (crates.io is at v0.0.5), so kick the tires before anything load-bearing.

    See also marimo-pair.

    Calvin #4: Hindsight Agent Memory That Learns

    AI agents forget everything between sessions — Hindsight gives them persistent memory that learns over time

    Simple three-method API: retain(), recall(), reflect() — store, retrieve, and reason over memories

    TEMPR retrieval runs semantic, keyword, graph, and temporal search in parallel for accurate results

    Automatically consolidates related facts into durable observations instead of piling up duplicates

    pip install hindsight-all runs the entire server in-process; integrates with LangChain, LlamaIndex, Pydantic AI, CrewAI, and more

    Extras

    Calvin:

    Clanker: A Word For The Machine

    **Ponytail — You know him. Long ponytail. Oval glasses. Has been at the company longer than the version control**

    **Klangk: Multi-User AI Sandboxing, Collaboration and Coding Platform**

    Cursor announces Origin

    performative-ui to quick start your new idea
    Michael:

    Astral Joins OpenAI: The Interview

    SpaceX to acquire Cursor

    And OpenAI renews Open Source support

    Portuguese subtitles are now available for Talk Python courses

    DSF is hiring including Six Feet Up support

    Joke: Oh Babe…
Más podcasts de Noticias
Acerca de Python Bytes
Python Bytes is a weekly podcast hosted by Michael Kennedy and Calvin Hendryx-Parker. The show is a short discussion on the headlines and noteworthy news in the Python, developer, and data science space.
Sitio web del podcast

Escucha Python Bytes, Julia en la onda y muchos más podcasts de todo el mundo con la aplicación de radio.es

Descarga la app gratuita: radio.es

  • Añadir radios y podcasts a favoritos
  • Transmisión por Wi-Fi y Bluetooth
  • Carplay & Android Auto compatible
  • Muchas otras funciones de la app