Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
TST: Followup corrections to #28205#28207
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
Make the changes suggested by@ianthomas23, and also mark the ipythontests as using their backend. While the backend is already checked foravailability at the top of the respective files, that only checkswhether it can be imported, not whether it can be set as the Matplotlibbackend. Adding the marker causes our pytest configuration to actuallycheck and skip the test if unavailable (e.g., on Linux without`(WAYLAND_)DISPLAY` set fails to set an interactive backend).
I'm milestoning this as 3.10 only so that the backport bot doesn't trigger; I pushed this backport directly to#28206. |
955432c
intomatplotlib:mainUh oh!
There was an error while loading.Please reload this page.
Remilestoned back to 3.9 post merge so no backport bot, but still will be caught by github stats/if we need to look back at it at some point/etc. |
Uh oh!
There was an error while loading.Please reload this page.
PR summary
Make the changes suggested by@ianthomas23 in#28205, and also mark the ipython tests as using their backend. While the backend is already checked for availability at the top of the respective files, that only checks whether it can be imported, not whether it can be set as the Matplotlib backend. Adding the marker causes our pytest configuration to actually check and skip the test if unavailable (e.g., on Linux without
(WAYLAND_)DISPLAY
set fails to set an interactive backend).PR checklist