-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
test_invalid_colormap: ValueError not raised #4215
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
@yarikoptic did you say you were using a customized back end? Also, can you show us what happens if you try to get a non-standard colormap from your version of matplotlib? This test, IIRC, just checks that plotting bubbles up the error from the mpl call to get the colormap. So if the other tests are passing, to me this suggests that either it's a matplotlib bug OR the Agg backend handles unknown colormaps differently. If there is variance in how colormaps are handled by backend, we should add a skip test at the start if directly asking for a bad colormap doesn't raise an error. |
Should have been @yarikoptic above (sorry about that!) |
For me even with the default interactive backend I get no exception while asking for the colormap
|
@yarikoptic I think t's because of the version of what you should see
my versions
|
☎️ pandas version help hotline, how can i help you? 😄 |
yep it's the version, just installed 1.1.1 and it returns |
i'll add a version check in there in the test |
actually u know what i'll raise if the color map is |
wow mpl gained a hefty 29MB from 1.1.1 to 1.2.1... |
that is under Agg backend and matplotlib 1.1.1~rc2-1
The text was updated successfully, but these errors were encountered: