commit | 00ba31c51c7a90ebfffec954b1dc28db015bfef3 | [log] [tgz] |
---|---|---|
author | Michael Spang <spang@google.com> | Thu Aug 26 17:03:48 2021 -0400 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 27 14:58:21 2021 +0000 |
tree | 8fa5f864e01d0d6f3a6266ad20a5b0df345e7b81 | |
parent | 28698d0aee4c112601d8b767b4160897443e8f5a [diff] |
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. No-Docs-Update-Reason: bug fix Change-Id: I3c13ccef171f5e9d17b6781341568e7b9909a161 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/58520 Commit-Queue: Michael Spang <spang@google.com> Reviewed-by: Rob Mohr <mohrr@google.com>
See our website: http://pigweed.dev