Skip to content

TST: handle change in pytest.importorskip behavior #28925

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 7, 2024

Conversation

tacaswell
Copy link
Member

It now warns if the module is found, but fails to import (rather than not existing and raising ModuleNotFound).

@tacaswell tacaswell added this to the v3.9.3 milestone Oct 2, 2024
tacaswell and others added 2 commits October 3, 2024 15:36
It now warns if the module is found, but fails to import (rather than
not existing and raising ModuleNotFound).
Apparently, Azure updated from macOS 12 to 14, which caused the change
in results outside of the Intel->ARM change.
@QuLogic
Copy link
Member

QuLogic commented Oct 3, 2024

Since #28923 didn't yet work, I've pushed an update to the tolerance here.

@tacaswell tacaswell merged commit df1e039 into matplotlib:main Oct 7, 2024
43 checks passed
@tacaswell tacaswell deleted the tst/pytest_tkinter branch October 7, 2024 14:08
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull request Oct 7, 2024
QuLogic pushed a commit to meeseeksmachine/matplotlib that referenced this pull request Oct 18, 2024
QuLogic added a commit that referenced this pull request Oct 18, 2024
…925-on-v3.9.x

Backport PR #28925 on branch v3.9.x (TST: handle change in pytest.importorskip behavior)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants