-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
obnoxious double warning at each script startup #7404
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
Comments
Apparently this is related to the TkAgg backend -- switching to wxagg makes the warnings disappear. |
attn @OceanWolf @fariza |
@vnoel You should only see these warnings if you have opted in to using the new experimental tool classes and/or tool_manager class as the warning suggests, but your comments seem to indicate that you have not done this, so I find this perplexing. By opted in, I mean either by making use of these new experimental classes directly; or in-directly by setting the |
@OceanWolf AFAIK, I do not use these experimental classes directly. I have only very little idea of what they are. My As for other libraries setting the rcParam for me, I still get the warnings by running this script:
so I don't think other libraries could be responsible. |
Ahh, I see the problem, we assumed that the toolbar rcParam set to None should still use the toolmanager but without a toolbar. An assumption we should re-evaluate. Thank you for bringing this to our attention. Until we get this fixed, in the next bug fix release, I have three options:
|
FIX: MPL should not use new tool manager unless explicited asked for. Closes #7404
For longer that I can remember, every time I start a script that imports matplotlib I get the following warnings:
These warnings are not only annoying, as I have no way to fix the code they refer to, but also lead to problems: by making the script output harder to parse, they often hide the actual output I want from the script. They are often longer than the useful script output.
I have seen suggestions to use the
warning
module to silence these messages, e.g.but I don't think this is a practical solution, as 1) I would need to add these two lines every time I create a new script that uses matplotlib (which is often), and 2) I would silence at the same time all the other warnings, that could be actually useful.
matplotlib 1.5.3 Python 2.7.12 on linux installed through conda, TkAgg backend.
Apparently not everyone sees those warnings.
The text was updated successfully, but these errors were encountered: