Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Setting markeredgecolor raises a warning #6480
Comments
|
@tacaswell Git is blaming you for this line. |
|
Those are both saying that we are comparing a string(Unicode) and an array. I have a caught memory that we fixed this on master. The change might have actually been updating Python or numpy underneath. |
|
@tacaswell We have fixed similar issues but I don't think we have fixed this one. |
tacaswell
added this to the
2.0.1 (next bug fix release)
milestone
Jun 15, 2016
|
I'm getting something slightly different on python 3.5:
Just running tests on a fix. |
dstansby
referenced
this issue
Dec 21, 2016
Merged
Fix warning when setting markeredgecolor to a numpy array #7657
QuLogic
closed this
in #7657
Dec 21, 2016
tacaswell
modified the milestone: 2.1 (next point release), 2.0.1 (next bug fix release)
Dec 22, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
u55 commentedMay 26, 2016
Hi matplotlib developers,
Setting
markeredgecolorto an RGB or RGBA numpy array now gives a warning in matplotlib 1.5.1. This was not a problem in version 1.4.3. Here is a minimal working example:In python 2.7, it gives this warning:
And in python 3.5, it gives this different warning:
Tested on Arch Linux.
--Thanks.