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

FIX: Use absolute imports in testing,tests and segment files #993

Closed
wants to merge 6 commits into from

Conversation

souravsingh
Copy link
Contributor

Changed some of the relative imports in testing and tests to use absolute imports.
Fixes a small part of #969

@quantshah
Copy link
Contributor

@souravsingh You shouldn't change the init files as arokem warned and I guess it will be better if we work by opening an issue first and then fixing it so that there are no conflicts later with multiple people working on the same thing. All the absolute error issues are referenced in #969

@souravsingh
Copy link
Contributor Author

@sahmed95 Sorry for this. I came to know this very late.

@quantshah
Copy link
Contributor

No issues. 😄 Even I had a doubt about this.

@quantshah
Copy link
Contributor

Also, I guess you can change segment too along with testing and tests here which will close #1000.

@souravsingh
Copy link
Contributor Author

@sahmed95 I have done the segment fixing in the latest commit for the PR

@quantshah
Copy link
Contributor

Then I would suggest you update the name of the fix to "Use absolute imports in segment, testing and tests"

@souravsingh souravsingh changed the title FIX: Use absolute imports in testing and tests files FIX: Use absolute imports in testing,tests and segment files Mar 22, 2016
@@ -5,8 +5,8 @@
IO_DATA_PATH = abspath(pjoin(dirname(__file__),
'..', 'io', 'tests', 'data'))

from .spherepoints import sphere_points
from .decorators import doctest_skip_parser
from dipy.testing.spherepoints import sphere_points
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd stay away from __init__ files, for now.

@arokem
Copy link
Contributor

arokem commented Mar 28, 2016

Hey @souravsingh - have you had a chance to take a look here? It would be great if you could revert the changes you made in the __init__ file

@souravsingh
Copy link
Contributor Author

My bad, I almost forgot about this.Thanks for reminding

@arokem
Copy link
Contributor

arokem commented Apr 4, 2016

This one needs a rebase.

@arokem
Copy link
Contributor

arokem commented Apr 13, 2016

Could you please rebase this on current master?

@arokem
Copy link
Contributor

arokem commented Oct 21, 2016

Superseded by #1134. Closing

@arokem arokem closed this Oct 21, 2016
MarcCote added a commit that referenced this pull request Oct 31, 2016
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.

3 participants