-
Notifications
You must be signed in to change notification settings - Fork 119
[WIP][don't merge yet] Python 3.4 compatibility #59
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
Conversation
- has_key is not available anymore - urllib and urlparse compatibility - open files as binary - string type compatibility - division compatibility
|
The CI results is also strange, it says "ImportError: No module named six" |
|
@blizzz if possible you could also try and adapt .travis.yml to have both a python2 + python3 target. Or if you can make all tests pass on Python 2.7 on Travis we could merge this earlier (Python 3 is probably broken anyway at this stage on master) and then we can all continue with separate PRs ? (I could look into making Travis run Python 3 CI) As you like. 😄 Edit: Python 2.4 => 2.7 |
|
Looking into making Travis run Python 3 tests here: #60 |
Could it be that we need to add it to install_requires in the setup.py? |
|
With regard to travis: i can have a look into it, but do not have a setup therefore, yet. Do you have a quick start guide? |
|
@blizzz for Travis I already started, here is the status: #60 (comment) |
|
Did this break Python 2 compat ? |
|
I mean, did Python 2 stuff still worked properly with this PR ? (even if Python 3 might still be broken) |
|
IIRC Py2 was unharmed. |
|
Possibly obsoleted by #146 ? |
Agreed. |
There is something left to do that I was not able to track down yet. I think i was close once, but missed the time to crunch on this :( A goal of course is to continue to support Python 2.7. The test against 2.7 run fine for me.
On 3.4 a test run reveals this: