For some time I’ve wanted the equivalent of Java’s ability to dump the stack trace of all currently running threads in Python as a means for debugging some hung processes. I finally found a solution and wired it up to the services’ http console:

I have a lot of SmugMug albums and sometimes I have a hard time tracking down in which Category and SubCategory one resides or whether I’ve updated all the albums to use square thumbnails – thus was born smugfind.

A question was asked on a dgrin thread about whether the SmugMug API supported building a tag cloud – it doesn’t. A responder suggested it would take far too long to generate one from the API since you’d have to trawl through every photo. This is indeed true, but you don’t have to do it serially. I consider the batchable interface for pysmug to be it’s selling point and building a tag cloud is the perfect demonstration.

I decided tonight was the night to try Python2.6a3 on my macbook pro with a goal of getting pysmug to run on it.

I just released version 0.4 of pysmug and I’m pretty happy with the additional functionality.

I finally found a non-trivial reason to implement a Python decorator. I make extensive use of Python keyword arguments in the pysmug API and map those spellings to SmugMug keyword arguments. The algorithm for converting a Python spelling to a SmugMug spelling is pretty straight forward and easily wrapped up in a function. Originally, the first line of every function required formatting the keywords into SmugMug-style spellings by calling self._prepare_keywords(**kwargs). It occurred to me this…

While I hammer away at erlsmug and try to figure out why it’s so much slower than pysmug and PycURL, I’m ready to release version 0.4 of pysmug.