Make code python3 compatible without running 2to3

[CyberDem0n]

It was not producing correct code anyway...

[coveralls]

Coverage decreased (-0.7%) to 88.7% when pulling f7e0db2 on CyberDem0n:py2py3compat into 33bee8f on bakwc:master.

[coveralls]

Coverage decreased (-0.06%) to 89.303% when pulling e951f27 on CyberDem0n:py2py3compat into 33bee8f on bakwc:master.

[coveralls]

Coverage decreased (-0.06%) to 89.303% when pulling e951f27 on CyberDem0n:py2py3compat into 33bee8f on bakwc:master.

[bakwc]

Thanks, great job! You are using range everywhere, may be it would be better to use xrange? There can be a performance issue when using range in python2.
Also coverage is crashing when running at travis python3.4 - I suggest to run test without coverage for python3.4.

[coveralls]

Coverage decreased (-0.06%) to 89.303% when pulling e663fe0 on CyberDem0n:py2py3compat into 33bee8f on bakwc:master.

[CyberDem0n]

You are using range everywhere, may be it would be better to use xrange? There can be a performance issue when using range in python2.

It's not everywhere, but only in benchmarks. I don't think that you will see a big difference on small numbers. In all critical parts xrange is used (and iteritems for py2 instead of items).

Also coverage is crashing when running at travis python3.4 - I suggest to run test without coverage for python3.4.

Sometimes it builds on travis are crashing without any visible reason and triggering build job solves it...
I did one more commit, if it wont help I will remove coverage for py34.

[CyberDem0n]

Funny, this time it crashed with python3.5

[coveralls]

Coverage decreased (-0.7%) to 88.645% when pulling 646b83c on CyberDem0n:py2py3compat into 33bee8f on bakwc:master.