A debate podcast from a style guide: two rules of PEP 8

Two AI hosts debate two rules of the PEP 8 style guide for Python. Hear it, copy the request, and see its cost and what our check found.

How this was made. Audio and video overviews, slide decks and infographics are made with Google's Gemini Notebook (formerly NotebookLM), on accounts that AutoContent operates. AutoContent has no agreement with Google. Google can limit or stop this access at any time.

The debate5 min 39 s

AI-generated with AutoContent APIDownload MP3 Full transcript (TXT)

What came out, and what we would change

We set style to debate and named the two rules to argue about: the 79-character line limit and the advice against extra spaces to align code. One host defends each rule and the other argues to relax it, as asked, and both quote the guide. The episode runs 5 min 39 s and ends without a winner.

The facts from the guide are right: the 79-character limit, up to 99 characters for a team that agrees on it, 72 characters for comments and docstrings, the reasons for the limit (several files side by side, review tools with two columns), the Pet Peeves rule against extra spaces around an assignment, and the guide's point that code is read much more often than it is written.

The hosts add things that are not in PEP 8: a shipping container, a house of cards, Tetris, a 13-inch laptop and 50 aligned variables as pictures, "three or four files" where the guide says several files, and the name of the writer who first wrote the foolish-consistency line, which PEP 8 does not give. "Do not name individual people" held only in part: the hosts do not name the authors of the guide, but they do name Emerson.

Use a debate to show both sides of a team decision before a review, or as a teaching episode. The episode took 5 min 7 s to generate and used 10 credits. The other styles are deep dive (the default), brief and critique.

Transcript excerpt

Speech-to-text of the output, not edited and without speaker labels. It is part of the sample output.

Sure. Like the 79-character limit, right? It prevents disruptive line wrapping across entirely different tooling environments. And similarly, banning extraneous spaces around assignment operators isn't just about aesthetics. It prevents messy diff pollution in your version control when variable names inevitably change. It's about predictable uniformity. But that uniformity has a hidden cost, I think. I mean, the guide's own philosophy borrows Emerson's famous quote, right? A foolish consistency is the hobgoblin of little minds. I knew you'd bring that up. Well, it's right there in the text. PEP 8 explicitly allows relaxing the line limits of 99 characters if a team agrees on it.

The exact request

The body that was sent to POST /content/Create, unchanged, and the same request as curl.

request.json

{
  "resources": [
    {
      "type": "website",
      "content": "https://peps.python.org/pep-0008/"
    }
  ],
  "outputType": "audio",
  "style": "debate",
  "text": "Debate two rules of this style guide: the 79-character line limit and the advice against extra spaces to align code. One host argues to keep each rule, the other argues to relax it, and both use examples from the guide. Do not name individual people.",
  "duration": "short",
  "language": "English"
}

curl

curl -X POST "https://api.autocontentapi.com/content/Create" \
  -H "Authorization: Bearer $AUTOCONTENT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"resources":[{"type":"website","content":"https://peps.python.org/pep-0008/"}],"outputType":"audio","style":"debate","text":"Debate two rules of this style guide: the 79-character line limit and the advice against extra spaces to align code. One host argues to keep each rule, the other argues to relax it, and both use examples from the guide. Do not name individual people.","duration":"short","language":"English"}'
# then poll until "status" is 100:
curl -H "Authorization: Bearer $AUTOCONTENT_API_KEY" "https://api.autocontentapi.com/content/Status/<request_id>"

How we checked it

Transcript: We transcribed the output with Whisper large-v3-turbo and compared the transcript with the source.
Language: Detected en, requested en.
Loudness: -23.7 LUFS integrated, true peak -5 dBTP.
Notes: The rules and numbers match PEP 8; the laptop and the 50 variables are the hosts' own pictures.
Checked on: 2026-11-02. Failed generations are run again and never published.

More examples

All examples