-
Notifications
You must be signed in to change notification settings - Fork 87
Bump numpy to 1.22.0 #289
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
Bump numpy to 1.22.0 #289
Conversation
Codecov Report
@@ Coverage Diff @@
## main #289 +/- ##
==========================================
+ Coverage 72.73% 72.87% +0.13%
==========================================
Files 95 96 +1
Lines 9176 9186 +10
==========================================
+ Hits 6674 6694 +20
+ Misses 2502 2492 -10
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
|
Looks like this bump may leave behind Python 3.7 support... let's hold on this. |
|
Per discussion this morning we're going to drop support for 3.7 as it EOLs in June anyway, so I will update this PR to do that as well. |
PyTorch can supply int32 inputs as SymInt values. This change adds explicit casts to them to fix the Windows CI. Fixed additional mypy errors #289 may be needed for python3.10
c978bec to
d0f5a55
Compare
d0f5a55 to
b6c256b
Compare
|
Oh man, this had the very unfortunate side effect of breaking Onnx builds on PyTorch. (It uses this script to install Onnx, and still supports python 3.7) https://github.com/pytorch/pytorch/actions/runs/3878248792/jobs/6614365795 |
|
Should we pin a commit in PyTorch for now? |
Onnx PR microsoft/onnxscript#289 expects numpy to be upgraded. That breaks pytorch's onnx builds. For now, mitigate by pinning the script to an older version until there's a proper solution Pull Request resolved: #91929 Approved by: https://github.com/justinchuby, https://github.com/kit1980
No description provided.