Comment 1 for bug 656178

I'm glad you have a successful workaround!

This is a bit strange, I wonder what's going on. At a guess it might be a unicode vs. bytes issue. I've got a simple patch to make that error slightly more informative, to hopefully confirm if that's the case.