-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
Deprecations for Matplotlib-3.0.0rc2 #2963
Comments
Thanks for reporting this! It is good to have users report what is coming up in upcoming matplotlib versions as we use the stable releases for ourselves and for testing. |
so you will test against matplotlib-3.0.0 (on Python 3.5+ branches), if it's released tomorrow ? |
I'll do my best. |
matplotlib-3.0 final is out. |
Thanks, I'll try it now. |
Okay I also see those deprecation warnings:
But I can't figure out where they're coming from, we do load and ship a custom rc file but it specifies none of the options it's warning about. |
Nevermind I found it, the default rcparams in matplotlib still set these values. We use a context manager to temporarily override the options and when they are restored the warnings are generated. |
Now fixed in #3013 |
unless it's an effect from previous packages tried in my notebook... checking |
don't know exactly how to set a
|
ok, workarounded in waiting of a better solution
|
I'll have another look, but I have mpl 3.0.0 and can't reproduce any warnings. |
Nevermind I can reproduce and I've got a fix. |
Merged that PR prematurely, still seeing those warnings. |
This one seems to have done it: #3058 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
with matplotlib-3.0.0rc2, some annoying deprecation warning do arrive
apparently, holoviews still generates the now unwanted parameters.
https://github.com/ioam/holoviews/blob/63cfac9e104b134f9dcb7eb0f1b16196df16e2db/holoviews/plotting/mpl/plot.py#L133..L134
see:
or
The text was updated successfully, but these errors were encountered: