improve handling of unicode and str in python2 code when using futurize

If python2  code uses unicode and str (to represent bytes).

When using futurize we add `from builtins import str` which breaks the behavior of the old `str` usage.

It would be nice to make it harder to mix up the two types when using futurize.