-
Notifications
You must be signed in to change notification settings - Fork 74k
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
Compatibility with NumPy 1.20+ #48935
Conversation
bnavigator
commented
May 6, 2021
- Fix the one already visible failure with NumPy 1.20 (Numpy v1.20+ compatibility #47691 (comment))
- Different approach than Update and align numpy versions in TensorFlow #48918: Relax upper bound instead of pinning to 1.20. Python 3.6 builds still need <1.20. (Per NEP 29, 1.20 dropped Python 3.6)
Just to notify, another user has submitted #49008 |
@bnavigator Can you please resolve conflicts? Thanks! |
@bnavigator Can you please resolve conflicts? Thanks! |
@gbaned: I resolved conflicts. But you developers clearly stick to the pinning strategy See also |
The mentioned commit is just a step in getting this handled. We will keep pinning dependencies in our CI, but |
I suggest, you make a PR and if it is merged before this one, I will happily revert 9a4642f. |
Could someone please trigger a kokoro run? @bhack, @mihaimaruseac? |
Sorry, I was OOO. It seems now we have wide ranges of deps in setup.py and this causes conflicts. |
Merge conflict resolved. |
Can't this be closed now according to #52380? |
Yeah, #47957 "fixed" the The changes in the requirements specifiers, the wrong comment about numpy install order and the wrong float shape tuples are still something to consider. |
Alright, fair enough. |
Please consider reproducers in #52657 closed this as this PR is supposed to address such issues. |
We now merged most of this PR. Disabled tests will be fixed ahead in the near future. |