Skip to content
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

Futurize to support Python 3 #28

Merged
merged 11 commits into from
Aug 10, 2017
Merged

Futurize to support Python 3 #28

merged 11 commits into from
Aug 10, 2017

Conversation

yurishkuro
Copy link
Contributor

futurize --stage2 -w opentracing_instrumentation tests

Yuri Shkuro added 3 commits July 30, 2017 15:18
`futurize --stage2 -w opentracing_instrumentation tests`
@yurishkuro yurishkuro requested a review from black-adder July 31, 2017 02:38
@oibe
Copy link

oibe commented Aug 1, 2017

Without specific domain knowledge this is difficult to review. I'm more interested in testing this diff. Is it enough to enable python 3.3 in travis, and make sure that our code works? What about parts for which we have no coverage?

@yurishkuro
Copy link
Contributor Author

yurishkuro commented Aug 10, 2017

@oibe - low coverage areas are unfortunate, but the changes applied are more or less the same across the board. In articular, urllib2 module is fairly well tested. There are some almost untested modules but they are not affected by this change (mainly sql related).

@yurishkuro yurishkuro merged commit bf03019 into master Aug 10, 2017
@yurishkuro yurishkuro deleted the py3 branch October 22, 2017 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants