Skip to content

Conversation

@jasongrout
Copy link
Member

No description provided.

@jasongrout
Copy link
Member Author

ping @ellisonbg and @jdfreder, and I guess @minrk too, for a review.

@minrk
Copy link
Member

minrk commented Dec 13, 2014

Okay by me. I guess the disadvantage would be that the user may not know that widgets are being used, or they may not be used at all, possibly just an unused import in a library. Hiding the actual source of the warning makes it harder to find out what's going on.

@jasongrout
Copy link
Member Author

@minrk: I'm -0 on hiding the file/line number info for that reason. @ellisonbg seemed to want it, though, and I think he has a point about non-confusing messages.

@minrk
Copy link
Member

minrk commented Dec 14, 2014

Can you do a quick rebase on master? That should get the fixed warning test.

@Carreau
Copy link
Member

Carreau commented Dec 14, 2014

relaunched travis.

Carreau added a commit that referenced this pull request Dec 15, 2014
Make the widget warning brief and easy to filter
@Carreau Carreau merged commit ca2f5b7 into ipython:master Dec 15, 2014
@Carreau Carreau added this to the 3.0 milestone Dec 15, 2014
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.

4 participants