You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Different 3d artist objects have slightly different call signatures for set_3d_properties (mostly with regards to kwargs). This should be consistent across all artist objects for mplot3d.
Not really a duplicate, but I can see how it could be seen that way. The problem is that the mplot3d API is quite muddy. There isn't a clear delineation of responsibilities among methods. Part of this is due to a lack of a consistent API in the core matplotlib for setting artist data, which #1483 touches on, and probably should be modified to be generic (there might already be an issue made for that).
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!
Activity
tacaswell commentedon Aug 17, 2014
This seems like a duplicate of #1483
@WeatherGod Can you close one of these?
petehuang commentedon Jan 3, 2017
@WeatherGod following up - can one of these be closed?
WeatherGod commentedon Jan 3, 2017
Not really a duplicate, but I can see how it could be seen that way. The problem is that the mplot3d API is quite muddy. There isn't a clear delineation of responsibilities among methods. Part of this is due to a lack of a consistent API in the core matplotlib for setting artist data, which #1483 touches on, and probably should be modified to be generic (there might already be an issue made for that).
github-actions commentedon Oct 9, 2023
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!