The PyLit tool dates from 2009. Here's a historical reference: http://wiki.c2.com/?PyLit It was Python 2. It had some minor problems. I forked it and cleaned it up for Python 3. Then I set it aside for a few years (six or so.) Dusting it off. Rearranging …

I blog. I write books. I write code. There are profound tool-chain issues in all three of these. Mostly, I'm tired of shabby "What You See Is All You Get" editing.

First. I use this blogger site as well as a Jive-based site at work. They're handy. But. There are …

I remain captivated by the ideals of Literate Programming. My fork of PyLit (https://github.com/slott56/PyLit-3) coupled with Sphinx seems to handle LP programming in a very elegant way.

It works like this.

1. Write RST files describing the problem and the solution. This includes the actual implementation code …

I've revised PyLit to work with Python3. See https://github.com/slott56/PyLit-3 The code seems to pass all the unit tests. The changes include Python3 revisions, plus a small change to handle trailing spaces in a sightly cleaner fashion. This was necessary because I have most of my editors …

Even though I wrote a literate programming tool (PyWeb) I slowly came to realize that it's not very good.

Mostly, I followed the Web/Weave world view and cribbed their markup syntax. It's not bad, but, the PyWeb markup is based on some presumptions about literate programming that were, perhaps …