Tested: Ran with and without constraints.txt on Windows
Change-Id: I1e18512329da7216e78fc496edb9242f8790353a
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/66441
Reviewed-by: Anthony DiGirolamo <tonymd@google.com>
Pigweed-Auto-Submit: Joe Ethier <jethier@google.com>
Commit-Queue: Auto-Submit <auto-submit@pigweed.google.com.iam.gserviceaccount.com>
The setup.sh script supports installation over an existing venv, but
could cause version conflicts relatively easily due to the
--force-reinstall flag. Instead, we now explicitly uninstall all the
wheels first.
The setup.bat script never supported installation over an existing venv,
and probably shouldn't have been using the --force-reinstall flag to
begin with.
Both scripts now support the inclusion of a "constraints.txt" file
side-by-side with the setup script itself. If such a file exists, it
will be provided to pip using the "-c" option when running installs.
Tested: Built and ran setup.sh from downstream project with and without
constraints file
Change-Id: I1b02f117d14a5a973a45df3a3117f9e8b03c4acf
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/65920
Reviewed-by: Anthony DiGirolamo <tonymd@google.com>
Commit-Queue: Joe Ethier <jethier@google.com>
