now it works on py3.2 as well, which doesn't support the explicit unicode literal.

from __future__ import unicode_literals is a major tool in making both worlds more compatible
Fixed a few more encoding related issues
intermediate commit on my way to a very reduced future for load time reduction
compiled a custom minifuture module, which contains only what we need.

It's working for py2 and py3, but the py2 performance still isn't great, nearly 70% slower than py3 (which by now is a tad faster than py2.6 pre changes
fixed unicode issues
Fixed py 3.2 issues
with these reductions, py2 is faster than it was before - the new string type is just enforced to unicode basically.

This means less secuity, as runtime type checks have been removed.
Reduced minifuture even more and removed most of its imports

Now it's truly minimal and just what I need.
The futurize command was a great help anyway as it fixed syntactic issues right away,
like assert and print statements.
Disabled slow test, which would also fail occasionally