Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Fix input check in Poly3DCollection.__init__#26532
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon! Remember to remove the If these instructions are inaccurate, feel free tosuggest an improvement. |
…532-on-v3.8.xBackport PR#26532 on branch v3.8.x (Fix input check in Poly3DCollection.__init__)
…nit__(cherry picked from commit267b7c0)
…3.7.xBackport PR#26532: Fix input check in Poly3DCollection.__init__
PR summary
PR checklist
So far higher level APIs like
plot_surface
andplot_trisurf
ensure the input for callingPoly3DCollection
is valid so usually we won't trigger the bug.By inspecting test code coverage report, this part of code has never been tested. A test is added to ensure it works.
code for generating coverage report specifying folder - for people who may be curious