Sigh, yeah, it is a bug. I have to check to see if it is still in effect
for v2.0. The work-around is to use "c" instead of "color".

On Mon, Feb 8, 2016 at 9:21 AM, Oren Amsalem notifications@github.com
wrote:

This simple example, should create an image with a single red circle

import matplotlibpyplot as ploty

from mpl_toolkitsmplot3d import Axes3D

plotyion()

fig = plotyfigure()
ax = figadd_subplot(111, projection='3d')
axscatter(0,0,0,color='red')

But this is what I get

[image: image]
https://camo.githubusercontent.com/268883ffc1dfefb8d5984981a5b3aa88bfa2dc44/68747470733a2f2f636c6f756467697468756275736572636f6e74656e74636f6d2f6173736574732f383938333731332f31323838373839332f65336535613435322d636537662d313165352d386633312d313536643636633162663432706e67

Is this a bug?

Thanks

—
Reply to this email directly or view it on GitHub
#5974.

So for plot you need to use 'color' to avoid py3k dict issues and with scatter you need to use 'c'?

Ugh, I didn't even think about that. Only that 'c' is explicitly processed
by scatter3d to delete masked points, and 'color' is passed through. Both
'c' and 'color' would then show up to the 2d call of scatter().

On Mon, Feb 8, 2016 at 12:33 PM, Thomas A Caswell notifications@github.com
wrote:

So for plot you need to use 'color' to avoid py3k dict issues and with
scatter you need to use 'c'?

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

By the way, facecolor is also not working, (edgecolor is working)

For the purposes of scatter, facecolor and color are pretty much aliases,
which get clobbered by the 'c' value that scatter3d is emitting...

On Sun, Feb 14, 2016 at 10:24 AM, Oren Amsalem notifications@github.com
wrote:

By the way, facecolor is also not working, (edgecolor is working)

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

I agree, this is a really sad issue.
I'm using (..., c=colors_vec, edgecolors='none', ...) to get expected default behaviour (no edge).
Are there any reasons for scatter kwargs not to be unified with other plotting functions?

@WeatherGod: Do you think this is an easy fix?

Might not fix everything, but adding kwarg normalization to the 3d
functions could probably fix some of this, I think?

On Mon, May 16, 2016 at 4:49 PM, Michael Droettboom <
notifications@github.com> wrote:

@WeatherGod https://github.com/WeatherGod: Do you think this is an easy
fix?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#5974 (comment)

#6426 might actually be relevant here?

On Mon, May 16, 2016 at 5:23 PM, Benjamin Root ben.v.root@gmail.com wrote:

Might not fix everything, but adding kwarg normalization to the 3d
functions could probably fix some of this, I think?

On Mon, May 16, 2016 at 4:49 PM, Michael Droettboom <
notifications@github.com> wrote:

@WeatherGod https://github.com/WeatherGod: Do you think this is an
easy fix?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#5974 (comment)

So, essentially, I need to update the scatter3d function to not emit 'c' in some cases, I think?

Yes.

I submitted PR #6439 that should fix this issue.

Closed via #6439