-
Notifications
You must be signed in to change notification settings - Fork 278
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
MNT: Add explicit support for Python 3.10 on windows #3706
Conversation
I don't yet understand why this the test isn't skipped on Jenkins, so I'll switch this to draft for now and remove it from the 4.0.2 milestone |
6a83d2e
to
56b32ea
Compare
Adding the backport label instead of the milestone to signal that it'd be cool to backport this on merge but it's not a blocker for the release |
67deb4f
to
43f6d75
Compare
Moving this to draft for now because it seems possible that a solution could be found quickly to avoid skipping the failing test. |
3a444d4
to
43f6d75
Compare
e77f4cc
to
4cfbb50
Compare
rebased on top of #3708 |
This is back in draft -- should it be marked ready? |
the only reason this is in draft mode is because it's based on #3708 |
Failures are unrelated. I'll mark it as ready for review when CI is stabilised |
33bdaa7
to
f750d88
Compare
…k on any test runner with any Python version
8850484
to
55bd8ee
Compare
c313120
to
55bd8ee
Compare
PR Summary
Complements #3543.
I've been testing this on my fork and I believe it is now ready.
I was also able to remove the pinning added in #3298 since upstream issue was resolved.
As a temporary measure I'm conditionally skipping the one test that fails with cartopy 0.20 (reported as #3705) because I don't think it is bad enough to prevent us from testing on windows + Python 3.10, the issue is linked in the test code. I assume the regression is actually upstream and should be reported there.