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

[Python][CI] Simplify python/requirements-wheel-test.txt file #43690

Closed
jorisvandenbossche opened this issue Aug 14, 2024 · 1 comment
Closed

Comments

@jorisvandenbossche
Copy link
Member

Related to #43539 (comment)

The current requirements-wheel-test.txt file has quite complex and detailed version pinning, varying per architecture. I think this can be simplified because we just want to test with some older version of numpy and pandas (and the exact version isn't that important).

The file is pinning to the most recent version of numpy for a given platform / python version. In the past, that made sense because we were building against the oldest supported numpy (and so testing with a different, more recent version). Nowadays we are actually building with the most recent version of numpy, and so then it might make sense to test with an older version of numpy.

jorisvandenbossche added a commit to jorisvandenbossche/arrow that referenced this issue Aug 14, 2024
jorisvandenbossche added a commit that referenced this issue Aug 22, 2024
…le (#43691)

### Rationale for this change

The current [requirements-wheel-test.txt](https://github.com/apache/arrow/blob/7c8909a144f2e8d593dc8ad363ac95b2865b04ca/python/requirements-wheel-test.txt) file has quite complex and detailed version pinning, varying per architecture. I think this can be simplified because we just want to test with some older version of numpy and pandas (and the exact version isn't that important).

* GitHub Issue: #43690

Authored-by: Joris Van den Bossche <[email protected]>
Signed-off-by: Joris Van den Bossche <[email protected]>
@jorisvandenbossche jorisvandenbossche added this to the 18.0.0 milestone Aug 22, 2024
@jorisvandenbossche
Copy link
Member Author

Issue resolved by pull request 43691
#43691

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant