commit 2fa2ec50448c941c3f5962804d3ebdefa9643209
author pigweed-integration-roller <pigweed-integration-roller@pigweed.google.com.iam.gserviceaccount.com> Fri Aug 27 15:01:09 2021 +0000
committer CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Fri Aug 27 15:24:21 2021 +0000
tree 749bd37db140a0cfc69e90e683007eac194e3727
parent 9d4ed966c1f219e1536c39a98b06ca71ab8f8f14

[roll third_party/pigweed] pw_env_setup: Upgrade setuptools in addition to pip

On Debian venv creation uses a fairly old version of setuptools:

  /usr/bin/python3 -m venv --upgrade /tmp/venv; /tmp/venv/bin/pip list
  Package       Version
  ------------- -------
  pip           20.3.4
  pkg-resources 0.0.0
  setuptools    44.1.1

This can cause issues installing packages, e.g.
https://github.com/pypa/setuptools_scm/issues/605

Upgrade setuptools in addition to pip. This matches the builtin behavior
of venv when passing the new --upgrade-deps option, which we could
eventually use to have these packages upgraded automatically upon venv
creation.

Also log the output of the upgrade as this might be useful later.
Debugging bootstrap is quite a bit harder when all of the output is
discarded.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/58520

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 28698d0aee4c112..00ba31c51c7a90e
Roller-URL: https://ci.chromium.org/b/8837734796053863953
Cq-Cl-Tag: roller-builder:pigweed-experimental-roller
Cq-Cl-Tag: roller-bid:8837734796053863953
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I25272a04982f97c241438e242a9a9af7f515d7a6
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/experimental/+/58640
Bot-Commit: Pigweed Integration Roller <pigweed-integration-roller@pigweed.google.com.iam.gserviceaccount.com>
Commit-Queue: Pigweed Integration Roller <pigweed-integration-roller@pigweed.google.com.iam.gserviceaccount.com>