Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
CI: Try skipping wx on py310#29443
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
The "are you installed" check is failing and printing a message. However,because the failure is on import loading shared objects, we still try to runtests against it.This is yet another example of the limitations of wheels.
It may also be worth sorting out how to try to uninstall what ever we tried to install if our checker fails. |
I spot checked that wx was not installed in a 3.10 run and was installed in a 3.11 run. |
See#29449 |
better handled by#29449 |
The "are you installed" check is failing and printing a message. However, because the failure is on import loading shared objects, we still try to run tests against it.
This is yet another example of the limitations of wheels.
We probably should debug why wxpython broke (it could either be the wheels changed to newly require libnotify or that the system dependencies changed and we stopped getting it by chance), but in the interest of un-breaking CI this just turns off wx for py310.