In that ps1 file, download the req.txt file from the prev step (you'll need to get it from the py/py repo) and install the packages it specifies.
In the windows build & test workflows, we also always install packages from the requirements.txt file if they’re not already installed.
Benefits
This would make future installations/upgrades easy by putting all the package changes in a single folder
We have dependencies defined in one place
We have safe guard in case the dependencies are not found in the AMI (which is expected for a small time window when a new package/upgrade is freshly added)
Goal: Enable pytorch devs to add/update pip packages for windows builds and tests in a single PR
Context
Today, if you're introducing a PR that takes a dependency on a new python package, for Windows you need to:
That's pretty tedious
The Ask
Instead we should do the following:
Benefits
cc @kit1980 @huydhn @clee2000