Older blog entries for fdrake (starting at number 2)

Well, Guido sent out the announcement about the move to Digital Creations today, so we can all breathe a sigh of relief:


Checkin mail from SourceForge this week hasn't been working at all, and we haven't been able to get ahold of them to see how we can help. It's really hard to develop anything when we don't know what anyone else is actually getting done, and patches aren't getting reviewed. Hopefully this will get fixed soon, but their MTA seems to be botched. That's what happens when you run sendmail with more traffic than it can handle. ;-(

I have managed to get a lot of tedious stuff done in spite of the SourceForge mail problems and wrapping up talks with our new employer. Most of the Python standard library has been run through Tim Peter's reindent.py script, which gets rid of hard tabs, trailing whitespace, blank lines at the end of the files, and, most importantly, converts everything to 4-space indents! Now we just need to write the style guide and include it in the standard Python documentation. The XML package documentation is starting to fall into place, and I've written a lot more of the "LaTeX Primer" for the Documenting Python manual.

The people at iUnivere don't seem to be interested in updating their "on-demand" published Python manuals to recent versions of the documentation, so I'm interested in finding someone who wants to publish short runs or on-demand copies of the most interesting parts of the Python documentation. One of the problems is that few people want to buy printed copies, and the other is that there's a lot of it. Or are people really keen on printing their own?

(If you know of a publisher of open source documentation interested in short-run work, please let me know about them!)

I've started to receive comments from people who want to see the bzip2 version of the documentation kept around, with the suggestion that people are more likely to switch if they knew how much shorter the download was. I've changed the documentation download page so the file sizes are available; we'll see if that makes a difference.

While between employers, I created a new project on SourceForge; it's called "GPath -- A C Library for Path Algebras. A neat idea; we'll have to see if it's really useful, though!

Enough chatter, I need to walk the dog.

11 Oct 2000 (updated 11 Oct 2000 at 02:56 UTC) »

The Python 2.0 release candidate is out, and there's more than ever to do in the documentation. I've been culling through my accumulated email and making all the little changes that seem to be needed just after I've packaged the documentation, and expect to have a lot of the really small nits fixed in time for the final release.

I also really need to buckle down and work on the documentation for the XML package; there's a lot of new material there that needs to be written, but Martin & Paul are working on new text for some of the components most in need of documentation. I need to integrate some changes from them and get a new development copy up soon; I'll push one in an hour or so, but that won't have the new XML documentation in it.

The conversion tool to convert the LaTeX sources needs to be updated to the new XML code (xml.dom.minidom); the DOM object constructors have changed, and there may be some changes related to hackery used to do things like change the names of existing elements. --sigh--

Today's big accomplishment: I got my INBOX back below 2500 messages! Don't send me any new ones. ;)

Well, the documentation for Python 2.0 is mostly stable, and shows a lot of improvement over the 1.6 documentation. There are still a few things to do to work around LaTeX2HTML problems, but that seems to always be the case. Every LaTeX2HTML problem pushes me that much closer to getting back to the XML conversion.

I've set things up so that I can easily publish the HTML for what's in my working directory at our FTP server, so it'll be easier for people to review the state of the documentation without having to install all the tools needed to build it from the LaTeX sources.

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!