Hi @tomka,
Apologies for the interruption here. There were two problems: Yesterday’s update contained a bug in its Python 2 backwards-compatibility, and our test suite failed to catch it. Both of these issues are now fixed, so this kind of thing shouldn’t be able to happen again.
Thanks very much for the bug report, and for your patience while we developed and shipped a fix.