Closed nicktimko closed 4 years ago
Forgot about the tests for some reason (see 3b04a39)... There was some trouble with ast.literal_eval
(maybe the replaces to reformat the string weren't enough?), so I just did an end-around and used JSON. Python 3 absolutely requires consistent space/tab usage across the entire file, so I cleaned that in run_tests.py
and for funsies the entire project after converting example.py
Again...my commit isn't super clean, but the code should be.
My apologies for not looking at this sooner, I will do so this week!
When will you add python3 compatibility?
More interest in python3 here :)
Python3 is the future!
+1
any luck with the python 3 yet ?
Btw the python 2.7 deprecation is 2020 - https://pythonclock.org/ My question is: what is the reason to move to Python3 now?
Any word on this?
+1
This has just been added!
A bit slap-dash, but nothing major modified. Tweaks generally break down into 4 categories:
print()
xrange
,izip
, forcing generator evaluation...)Another minor tweak was explicitly encoding a string (unicode in Python 3) into UTF-8 so it could be hashed.
With the changes, running
example.py
works just fine, but let me know if you want the commits cleaned up a bit.