c=color not changing line color

[divenex]

In Matplotlib 1.4.3

plt.plot([0,1], c='lime', linewidth=20)

produces a blue line, while

plt.plot([0,1], color='lime', linewidth=20)

produces a green one as expected.

[tacaswell]

Did using c used to work?

[Tillsten]

I can not reproduce that one, c works.

[NelleV]

I can't reproduce either but I only tried on master.

Did using c used to work?

—
Reply to this email directly or view it on GitHub
#4162 (comment)
.

[divenex]

Yes, using c=color used to work for various matplotlib releases. I noticed the problem because the plots produced by some of my code suddenly changed colors after updating matplotlib.

[efiring]

"c" and "color" are listed in the Line2D docstring as synonyms, so they should work identically as kwargs in plot(). The problem is present on master as well as 1.4.3.

[tacaswell]

Have a hunch that https://github.com/matplotlib/matplotlib/pull/3855/files caused this regression but don't have time to chase this down today.

[tacaswell]

github-foo linking magic #3855

[efiring]

Now, what I don't understand is why I can reproduce this on a recent master, and @NelleV cannot. I'm on Python 3.4:

In [1]: import matplotlib

In [2]: matplotlib.__version__
'1.5.dev1'

In [3]: %matplotlib qt

In [4]: import matplotlib.pyplot as plt

In [5]: plt.plot([0,1], c='lime', linewidth=20)
[<matplotlib.lines.Line2D at 0x1155ec080>]

That gives me a blue line.

[WeatherGod]

I think I know what is happening (for once, my futile attempts at
refactoring color-cycling bears some useful knowledge!)

There are two dictionaries passed around for various reasons. While this
change improved things by not only retrieving data from either
dictionaries, but also saving information to both. Unfortunately, the code
doesn't check for the synonyms. Without "color' in the second dictionary,
the Line2D object was getting the value for 'c'. Now, 'color' shows up from
the color-cycling, overriding the 'c' argument.

On Thu, Feb 26, 2015 at 1:06 PM, Thomas A Caswell notifications@github.com
wrote:

Have a hunch that https://github.com/matplotlib/matplotlib/pull/3855/files
caused this regression but don't have time to chase this down today.

—
Reply to this email directly or view it on GitHub
#4162 (comment)
.

[WeatherGod]

Could be different values for color-cycling in the rc?

On Thu, Feb 26, 2015 at 1:07 PM, Eric Firing notifications@github.com
wrote:

Now, what I don't understand is why I can reproduce this on a recent
master, and @NelleV https://github.com/NelleV cannot. I'm on Python 3.4:

In [1]: import matplotlib

In [2]: matplotlib.version
'1.5.dev1'

In [3]: %matplotlib qt

In [4]: import matplotlib.pyplot as plt

In [5]: plt.plot([0,1], c='lime', linewidth=20)
[<matplotlib.lines.Line2D at 0x1155ec080>]

That gives me a blue line.

—
Reply to this email directly or view it on GitHub
#4162 (comment)
.

[mwaskom]

Just ran into this issue in the seaborn tests and can confirm that I see it only on Python 3.4, but not on Python 3.3 or 2.7.