pdit: The Python Un-Notebook for Coding Agents

#1

Post by ichverstehe » Fri, Feb 13, 2026, 11:40 AM UTC

pdit: The Python Un-Notebook for Coding Agents
harry.vangberg.name

Re: pdit: The Python Un-Notebook for Coding Agents

#2

Post by aanet » Fri, Feb 13, 2026, 12:21 PM UTC

I like it. I could see myself using it for quick verification of code.

What does this mean though: "By default, pdit shows output from each top level expression" ?

Re: pdit: The Python Un-Notebook for Coding Agents

#3

Post by ichverstehe » Fri, Feb 13, 2026, 12:50 PM UTC

aanet wrote: post #2

I like it. I could see myself using it for quick verification of code. What does this mean though: "By default, pdit shows output from each top level expression" ?

Consider a notebook with a cell with two lines of code:

  [1, 2, 3]
  "foo bar"

The default in notebooks is to just render/show the value of the last expression (`"foo bar"`). In pdit, the value of all top-level expressions are rendered/shown:

  [1, 2, 3] #=> [1, 2, 3]
  "foo bar" #=> "foo bar"

In that way it is more like a REPL than a notebook, you could say.

Re: pdit: The Python Un-Notebook for Coding Agents

#4

Post by aanet » Fri, Feb 13, 2026, 2:14 PM UTC

ichverstehe wrote: post #3

aanet wrote: post #2

I like it. I could see myself using it for quick verification of code. What does this mean though: "By default, pdit shows output from each top level expression" ?

Consider a notebook with a cell with two lines of code: [1, 2, 3] "foo bar" The default in notebooks is to just render/show the value of the last expression (`"foo bar"`). In pdit, the value of all top-level expressions are rendered/shown: [1, 2, 3] #=> [1, 2, 3] "foo bar" #=> "foo bar" In that way it is more like a REPL than a notebook, you could say.

ah I see, got it. Thanks