I have a heavily threaded Python program that dies every now and thenwith a mysterious exception (that as far as I can see just shouldn'thappen, which means that I don't completely understand my code).

My off and on attempts to debug this have pointed out a frustratingproblem in Python's (lack of) support for debugging threaded Pythonprograms: there's no such thing as a global exception, something thatwill freeze, backtrace, and terminate all threads when an erroroccurs.

It's pretty simple:

• change your syndication feed URL
• but don't remove or redirect the old feed, just stop updating it
• and don't put up an entry about it (visible in the old feed).

Readers who are not especially attentive may not notice for weeks, onlyvaguely wondering if you've taken a vacation or something. Especially ifthey read a fair amount of feeds and are behind in their reading.

As far as I've gathered, most feed readers are perfectly willing to

Today we had a fun problem created by a combination of entirely rational find optimizations and a corrupted, damaged filesystem.

An important Linux server took some kind of hit that turned some filesinto directories (with contents, presumably stolen from some other poordirectory). We found some but were pretty sure there were others lurkingout there too, and wanted to do our best to find them. (If only tofigure out what we needed to restore from the last good backups.)

As it happens, most of the