| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Do not fully understand what changed, but without this change `walk_stack` would start 2 frames higher (in the test module, not in backend_bases) which would mean we never saw the frame with `print_figure` and hence was getting warnings which we converted to failures on a vast majority of the tests. I suspect that this is related to the fast-Python work and avoiding making unneeded structures during the calls, but chased that theory down yet. Discovered on a commit between py311a2 and py311a3.
We should have pulled this out in mpl3.5
|
#21395 is a possible implementation of the followup (which I agree is too large for a patch release). |
Sorry, something went wrong.
|
Ah, great, I missed that PR existed. Glad I did not waste time trying to sort out how to do that removal :) |
Sorry, something went wrong.
…705-on-v3.5.x Backport PR #21705 on branch v3.5.x (MNT: make print_figure kwarg wrapper support py311)
| Back | FazBrowse Home | New Git URL |
PR Summary
Do not fully understand what changed, but without this change walk_stack
would start 2 frames higher (in the test module, not in backend_bases) which
would mean we never saw the frame with print_figure and hence was getting
warnings which we converted to failures on a vast majority of the tests.
I suspect that this is related to the fast-Python work and avoiding making
unneeded structures during the calls, but chased that theory down yet.
Discovered on a commit between py311a2 and py311a3.
This will need a followup PR to main that rips out almost all of this code. We should have ripped it out in mpl35, but do not think we should do that in a patch release so also updated the deprecation date.
PR Checklist
Tests and Styling
Documentation