Uploaded November 2026 | Updated November 2026, 3 hours ago
In this episode of AI Coding with Dr. Chuck, I do some maintenance on the Python for Everybody website after learning that Trinket has shut down when I received an email from the CTO of coddy.tech.
https://coddy.tech/
Rather than leaving the old integration disabled or carrying unused code indefinitely, I create a release plateau and remove the Trinket-specific book, scripts, pages, and references from the codebase. Old Trinket URLs are redirected back to the regular Python for Everybody book.
What starts as a straightforward content cleanup turns into a broader maintenance session. Running the book-generation tools exposes some older Pandoc and LaTeX issues, including a \pandocbounded problem and a stray control character. I also revisit the scripts that generate the HTML, PDF, and ZIP versions of the book.
From there, the work expands into Git pre-commit hooks so generated book archives can stay synchronized with source changes without relying entirely on separate cron jobs.
It is a useful example of working with AI on an established codebase: the task begins with deleting obsolete code, but exercising the surrounding system reveals several pieces of infrastructure worth cleaning up at the same time.
Topics include:
Python for Everybody
Trinket shutdown
Legacy code cleanup
Cotty.Tech
Website maintenance
Pandoc
LaTeX
PDF generation
HTML book generation
Shell scripting
ZIP generation
Git pre-commit hooks
Release tags and rollback points
Production deployment
AI-assisted software development
In this episode of AI Coding with Dr. Chuck, I do some maintenance on the Python for Everybody website after learning that Trinket has shut down when I received an email from the CTO of coddy.tech.
https://coddy.tech/
Rather than leaving the old integration disabled or carrying unused code indefinitely, I create a release plateau and remove the Trinket-specific book, scripts, pages, and references from the codebase. Old Trinket URLs are redirected back to the regular Python for Everybody book.
What starts as a straightforward content cleanup turns into a broader maintenance session. Running the book-generation tools exposes some older Pandoc and LaTeX issues, including a \pandocbounded problem and a stray control character. I also revisit the scripts that generate the HTML, PDF, and ZIP versions of the book.
From there, the work expands into Git pre-commit hooks so generated book archives can stay synchronized with source changes without relying entirely on separate cron jobs.
It is a useful example of working with AI on an established codebase: the task begins with deleting obsolete code, but exercising the surrounding system reveals several pieces of infrastructure worth cleaning up at the same time.
Topics include:
Python for Everybody
Trinket shutdown
Legacy code cleanup
Cotty.Tech
Website maintenance
Pandoc
LaTeX
PDF generation
HTML book generation
Shell scripting
ZIP generation
Git pre-commit hooks
Release tags and rollback points
Production deployment
AI-assisted software development










