-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Merge 1.5.x to 2.x #6443
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
Merge 1.5.x to 2.x #6443
Conversation
Defer to 2D scatter() for handling of 'c'. Closes matplotlib#5974.
When passed arguments that are only used when creating a new MovieWriter instance, raise an error if writer is an existing instance rather than silently ignoring the arguments. Also document the fact that these arguments are invalid in that case.
Animation error handling (Fixes matplotlib#6416)
@@ -2271,11 +2273,12 @@ def scatter(self, xs, ys, zs=0, zdir='z', s=20, c=None, depthshade=True, | |||
|
|||
if c is None: | |||
c = self._get_lines.get_next_color() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when did we add cycling support directly into scatter3d? I would have let the 2D scatter handle that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Went in in 48d5b6b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I see why (need to handle the None
case). However, it should have still deferred to the 2d scatter. So, for the merge, have it so that it accepts my changes from v1.5 over what is in master for this portion of the code. My version defers the handling of None
to 2d scatter, which is the correct course of action.
Yeah, the color cycling support and my fix for scatter3d are now clashing:
Cycling needs to be defered to the 2d function because all of the input handling needs to be figured out first. |
Since we now know the performance is so bad, this should discourage its use and flag it as something special. Also, use () in more places
PRF: Speed up point_in_path and friends
Ditto what @WeatherGod said: deferring to the 2D makes sense. |
I will try getting to working on this in the weekend but if anyone wants to work on it before hand feel free to replace and close this |
31d7f08
to
712500d
Compare
@WeatherGod I think this should resolve the 3d scatter conflict correctly. @mdboom I had to resolve another conflict in _image.h due to the merge of #6450 but it seems to only be due to code removed so I think it should keep the improved performance |
yes, that conflict resolution looks good to me. Thanks! |
There was a conflict in axes3d.py so letting Travis verify that this works. @WeatherGod Can you have a look at that change?