-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
move to python3? #3
Comments
Interesting ... not obvious while file actually had the unicode error? |
I am not sure. It may be an error in the refactoring code too. It does a huge amount of refactoring and then it returns (longer version)
|
It was a bogus copyright sign in pim/lookout.py |
By looking at the file it was processing just before the error |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There was a major change in syntax in python as it moved to python3.
It looks like the move can be automated
https://stackoverflow.com/questions/25445439/what-does-syntaxerror-missing-parentheses-in-call-to-print-mean-in-python
I tried
2to3 . -w
which changes 142 files. But it gets stuck onAnd I am not knowledgeable enough to continue much further at present.
The text was updated successfully, but these errors were encountered: