Skip to content

CI: Reduce duplicate pyarrow version testing #50451

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 3 commits into from
Dec 28, 2022

Conversation

mroeschke
Copy link
Member

@mroeschke mroeschke commented Dec 27, 2022

We probably don't need to be testing multiple permutations of pyarrow version & Python version in the CI. Instead:

  • PY310 builds will test pyarrow version 6 - 10
  • PY38 & 39 builds will test pyarrow = 10

@mroeschke mroeschke added CI Continuous Integration Arrow pyarrow functionality labels Dec 27, 2022
@phofl
Copy link
Member

phofl commented Dec 27, 2022

Id be more comfortable with testing all versions on python 3.10 or maybe 3.9.

We will remove support for 3.8 soonish, so I think this makes more sense?

@mroeschke
Copy link
Member Author

Id be more comfortable with testing all versions on python 3.10 or maybe 3.9.

We will remove support for 3.8 soonish, so I think this makes more sense?

Makes sense, will run the different versions on 3.10 instead

@phofl phofl added this to the 2.0 milestone Dec 28, 2022
@phofl phofl merged commit dd8b718 into pandas-dev:main Dec 28, 2022
@phofl
Copy link
Member

phofl commented Dec 28, 2022

thx @mroeschke

@mroeschke mroeschke deleted the ci/pyarrow/update branch December 28, 2022 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Arrow pyarrow functionality CI Continuous Integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants