Currently it appears that using six.moves in threaded code isn't
working as expected (something there in six does not appear to
be thread safe) so until this is fixed avoid using those moves
in functions in the examples and in the utility code (and instead
import the moved function at the top of the module in code to
avoid any threaded usage problems).
Upstream bug filed at:
https://bitbucket.org/gutworth/six/issue/98/
Fixes bug 1377514
Change-Id: I3fc1819df8fb42d0c3d394bbc7d047b09152af68