Skip to content

Conversation

mroeschke
Copy link
Member

@mroeschke mroeschke commented May 1, 2022

Hoping to supersede #46386. cc @lithomas1

While the job queue bandwidth is larger now, probably don't need to test different pyarrow versions with different Python versions. Instead:

  • PY38 will test pyarrow 5, 6, 7
  • PY39 and PY310 will just test pyarrow 5

@mroeschke mroeschke added CI Continuous Integration Arrow pyarrow functionality labels May 1, 2022
@mroeschke mroeschke modified the milestones: 1.5, 1.4.3 May 1, 2022
Copy link
Contributor

@lithomas1 lithomas1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for picking this up! Do you know if we should remove pyarrow from the env files, given that we're installing it manually here?

@mroeschke
Copy link
Member Author

Thanks for picking this up! Do you know if we should remove pyarrow from the env files, given that we're installing it manually here?

I don't think we can since the Azure Windows/MacOS builds use these files and don't install pyarrow manually

@jreback jreback merged commit 9465321 into pandas-dev:main May 2, 2022
@jreback
Copy link
Contributor

jreback commented May 2, 2022

@meeseeksdev backport 1.4.x

meeseeksmachine pushed a commit to meeseeksmachine/pandas that referenced this pull request May 2, 2022
jreback pushed a commit that referenced this pull request May 2, 2022
@mroeschke mroeschke deleted the ci/spcific_pyarrow branch May 2, 2022 21:37
yehoshuadimarsky pushed a commit to yehoshuadimarsky/pandas that referenced this pull request Jul 13, 2022
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.

3 participants