Closed xuzhao9 closed 1 week ago
@xuzhao9 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.
@xuzhao9 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.
We probably can add a constraint to the numpy version by dynamically adding a numpy_constraint.txt
file during the installation.
I think it is reasonable to guarantee that numpy version does not change when the models are being installed.
@xuzhao9 merged this pull request in pytorch/benchmark@62e2609a269f8ba394d01b82a71a037a4b240f75.
When there is a big numpy version bump (1.21.2 -> 2.0.0),
pip install
will somehow automatically upgrade numpy version to 2.0.0 even when the old version (1.21.2) has been installed.Therefore, we have to hardcode numpy version both globally and for the models whose install will cause numpy to unexpectedly upgrade. Since downstream CI supports Python 3.8 as the lowest supported Python version, we have to pin numpy version to the lowest version used in the downstream CI.