| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Thank you for opening your first PR into Matplotlib!
If you have not heard from us in a while, please feel free to ping @matplotlib/developers or anyone who has commented on the PR. Most of our reviewers are volunteers and sometimes things fall through the cracks.
You can also join us on gitter for real-time discussion.
For details on testing, writing docs, and our review process, please see the developer guide
We strive to be a welcoming and open project. Please follow our Code of Conduct.
Sorry, something went wrong.
|
I think it'd be better to not do this so late, since this is in the draw call. Then the array can be done once instead of every refresh, which could be a bit slow. |
Sorry, something went wrong.
|
I think this should be changed as well: matplotlib/lib/mpl_toolkits/mplot3d/art3d.py Lines 563 to 566 in 3992fb0 Both changing the name from _linewidth3d to _linewidths3d and converting into an np-array. |
Sorry, something went wrong.
|
Maybe one can also add a check_figures_equal test that uses the set_linewidth method for one of the figures and the keyword argument for the other? (See the test just below the one you added to see how they work.) |
Sorry, something went wrong.
To clarify, since set_linewidths is already there in the test case that you are pointing to (and since self._linewidths was already getting properly set in the super() call it worked ok for scalars as tested), would you like me to add another test like that, but testing that array-likes can be set via keyword argument and setter? Edit: added, can remove if not needed. |
Sorry, something went wrong.
|
Considering the spelling error, I do not think that it was actually properly tested, so ideally there should be a test that does set_linewidth and relies on that the spelling is correct. (The spelling error was introduced in #19812 btw.) |
Sorry, something went wrong.
|
The test which I added in 2bdbdca should cover that. The documentation build seems to be failing, is there anything I should do, or is it intermittent CI issue? |
Sorry, something went wrong.
|
@krassowski looking at the docs build logs, I think this was just an intermittent CI issue. I don't think there's a way to re-trigger the tests through the github gui, but if you do a git commit --amend followed by a git push -f I believe that should change the timestamp on your last commit and cause the CI tests to rerun. |
Sorry, something went wrong.
|
Thanks, all checks have passed now 🎉 |
Sorry, something went wrong.
|
A gentle ping on this PR :) |
Sorry, something went wrong.
|
Congratulations on your first merged Matplotlib PR @krassowski 🎉 Hopefully we will hear from you again! Also thank you for the gentle ping! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Summary
Fixes #23433 by casting self._linewidths3d to np.array at the latest stage possible and adds a test to ensure it works.
The casting step could alternatively be moved to happen earlier in the code logic in set_linewidth and in set_3d_properties, but I went for the simplest solution possible. Let me know if you want to change that (in that case, is self._linewidth3d = lw a typo? should it be _linewidths3d?)
PR Checklist
Tests and Styling
Documentation