-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[DO NOT MERGE] only pin down numpy==2.2.1 and pandas==2.2.3 for 2.62.0 #33627
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
[DO NOT MERGE] only pin down numpy==2.2.1 and pandas==2.2.3 for 2.62.0 #33627
Conversation
|
Assigning reviewers. If you would like to opt out of this review, comment R: @damccorm for label python. Available commands:
The PR bot will only process comments in the main thread (not review comments). |
|
I would merge something similar on main, but not not on release branch |
|
question is, why numpy is not bumped up. need to create a docker container instance from a released container and run pipdeptree |
|
It's from: |
https://github.com/apache/beam/blob/master/sdks/python/setup.py#L411 this causes pandas stays with 2.1.4 |
|
|
|
decided to fix this with 2.63.0. |

pin numpy==2.0.2 for Python 3.9. Others use numpy==2.2.1.
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>instead.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.