It uses PIL to render the Sparklines to files. For the most part it creates horrifyingly ugly sparklines, and while the API is quite similar to Sparklines.js it isn't necessarily perfect. You might say that I am releasing it on meritless whim. It was originally intended to support a web service that would dynamically generate sparklines for users on the website via Sparklines.js, and would then allow users to export a copy using the Python library to generate an image file. It actually works fairly well for that purpose (the API is slightly different, but nothing you can't correct somewhere in your application's logic), except for the images generated by the Python library being so hideous (this isn't entirely a bluff, the prototype of the web application I was working on did exactly that).
For what it's worth, I don't think the putrid appearance is something that can't be overcome, just requires a bit of attention to it, that's all.
The Porting Experience
Hopefully the port is mildly useful. I don't have much intention of supporting this one, but if you have questions I'll do my best to assist.