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

Add a warning on attempted import. #1977

Merged
merged 5 commits into from
Oct 17, 2019
Merged

Conversation

arokem
Copy link
Contributor

@arokem arokem commented Oct 2, 2019

Would this properly address #1976 ?

The cryptic error is still raised, but is preceded by a warning:
Screen Shot 2019-10-02 at 5 38 01 AM

@pep8speaks
Copy link

pep8speaks commented Oct 2, 2019

Hello @arokem, Thank you for updating !

Cheers ! There are no PEP8 issues in this Pull Request. 🍻

Comment last updated at 2019-10-16 17:52:34 UTC

Copy link
Member

@skoudoro skoudoro left a comment

Choose a reason for hiding this comment

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

Looks good, Thank you for that @arokem!

Can you add a quick test?

@skoudoro
Copy link
Member

Any chance to have a test for this PR @arokem?

@codecov
Copy link

codecov bot commented Oct 10, 2019

Codecov Report

Merging #1977 into master will increase coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1977      +/-   ##
==========================================
+ Coverage   84.09%   84.09%   +<.01%     
==========================================
  Files         118      118              
  Lines       15018    15020       +2     
  Branches     2372     2372              
==========================================
+ Hits        12629    12631       +2     
  Misses       1829     1829              
  Partials      560      560
Impacted Files Coverage Δ
dipy/viz/__init__.py 91.66% <100%> (+1.66%) ⬆️

@arokem
Copy link
Contributor Author

arokem commented Oct 10, 2019

Sorry - yes - I have this for now. But it seems to be failing...

I don't understand why the warning is not being captured by catch_warnings. It's definitely being emitted!

@skoudoro
Copy link
Member

Thanks! Maybe because of a warning filter rules. I do not know which one but I got this problem once.

@skoudoro skoudoro added this to the 1.1 milestone Oct 15, 2019
@skoudoro
Copy link
Member

Thank you for this @arokem! Merging

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