[roll] Roll third_party/pigweed pw_build: Python script for the build_wheel target

This adds generate_python_wheel.py to replace the direct call to
python -m build within GN.

The behavior remains the same with two additions:

- Stale wheel files from old builds are deleted first
- After the wheel is created a 'requirements.txt' is written with the
  package name==version and the sha256 line. This will be used in a
  followup CL to install Python wheel artifacts with: `pip install
  --require-hashes`

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/153710
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Original-Revision: bd9a7eb032a379aa85174c2f8a1672ca06faf262
GitOrigin-RevId: bd9667c3929ef91fe774337000ac0f21c4084d4c
Change-Id: I71ee3fd363f0923ada0f3cc27999ad3efa11ad7e
1 file changed
tree: 96f2f8c13959a70ed42e5bdcf63a53bf85835509
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.