Skip to content
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

Merged
merged 2 commits into from
Jan 19, 2022

Conversation

neutrinoceros
Copy link
Member

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.

@neutrinoceros neutrinoceros added this to the 4.0.2 milestone Dec 3, 2021
@neutrinoceros neutrinoceros added the enhancement Making something better label Dec 3, 2021
@neutrinoceros neutrinoceros changed the title MNT: Add explicit support for Python 3.10 on windows - switch pytest + windows job to Python 3.10 MNT: Add explicit support for Python 3.10 on windows Dec 3, 2021
@neutrinoceros neutrinoceros added infrastructure Related to CI, versioning, websites, organizational issues, etc pytest labels Dec 3, 2021
@neutrinoceros
Copy link
Member Author

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

@neutrinoceros neutrinoceros marked this pull request as draft December 3, 2021 16:42
@neutrinoceros neutrinoceros removed this from the 4.0.2 milestone Dec 3, 2021
@neutrinoceros neutrinoceros force-pushed the py310_support_win branch 2 times, most recently from 6a83d2e to 56b32ea Compare December 3, 2021 18:26
@neutrinoceros neutrinoceros added the backport-yt-4.0.x on-merge: backport to yt-4.0.x label Dec 3, 2021
@neutrinoceros
Copy link
Member Author

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

@neutrinoceros neutrinoceros marked this pull request as ready for review December 3, 2021 19:14
@neutrinoceros neutrinoceros marked this pull request as draft December 5, 2021 17:33
@neutrinoceros
Copy link
Member Author

Moving this to draft for now because it seems possible that a solution could be found quickly to avoid skipping the failing test.

@neutrinoceros
Copy link
Member Author

rebased on top of #3708

@matthewturk
Copy link
Member

This is back in draft -- should it be marked ready?

@neutrinoceros
Copy link
Member Author

the only reason this is in draft mode is because it's based on #3708
Now if you'd like, feel free to merge this directly, in which case I'll close and delete the other branch

@neutrinoceros
Copy link
Member Author

Failures are unrelated. I'll mark it as ready for review when CI is stabilised

@neutrinoceros neutrinoceros force-pushed the py310_support_win branch 2 times, most recently from 33bdaa7 to f750d88 Compare January 10, 2022 11:33
@neutrinoceros neutrinoceros marked this pull request as ready for review January 10, 2022 14:13
@neutrinoceros neutrinoceros removed the backport-yt-4.0.x on-merge: backport to yt-4.0.x label Jan 12, 2022
@matthewturk matthewturk merged commit 1295019 into yt-project:main Jan 19, 2022
@neutrinoceros neutrinoceros deleted the py310_support_win branch January 19, 2022 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Making something better infrastructure Related to CI, versioning, websites, organizational issues, etc pytest
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants