-
Notifications
You must be signed in to change notification settings - Fork 261
Import BytesIO from io #519
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
Looks good - are you happy with just this change, or are there more to come? Would you mind rebasing? |
Yeah, I'll rebase before this goes in. I'm a little curious why that first one failed, so I want to run these tests. I'll ping you once I've stopped tinkering. |
Codecov Report
@@ Coverage Diff @@
## master #519 +/- ##
=======================================
Coverage 94.14% 94.14%
=======================================
Files 175 175
Lines 23887 23887
Branches 2568 2568
=======================================
Hits 22489 22489
Misses 918 918
Partials 480 480
Continue to review full report at Codecov.
|
I did try this refactoring a while back, but ran into the same trouble and backed off. The differences come from the fact that |
Yeah, not planning on refactoring, but I do want to see which ones are safe to switch. Latest commit looks to be building fine on Travis. At least now we're down to: $ grep -rI IO nibabel | grep 'six import'
nibabel/externals/tests/test_six.py: from six import BytesIO
nibabel/tests/test_analyze.py:from six import BytesIO, StringIO
nibabel/tests/test_batteryrunners.py:from six import StringIO
nibabel/tests/test_wrapstruct.py:from six import StringIO If someone decides to tackle those last few imports, at least the scope will be clearer. Squashing... |
Rebased. I'll merge when (assuming) the tests pass, unless you'd rather do the honors? |
Go for it. |
This PR also updates a bunch of
from six import BytesIO
imports I found while making sure that was the only thing still importing fromexternals.six
.