1713377 - Fetch pure-python wheels if possible when vendoring

Status: RESOLVED FIXED

(Firefox Build System :: Mach Core, enhancement, P2)

Description

[Mitchell Hentges [:mhentges] 🦀]

Fetching wheels instead of tar.gz files has two benefits:

1. There's less files, since we just get the "pure" Python and no docs, build files, etc
2. As we start running the pip resolver against our packages, it needs to be able to understand them, and some packages (like zipp) don't like having setup.py run from the release.

Comment 1

[Mitchell Hentges [:mhentges] 🦀]

Attachment: Bug 1713377: Change vendoring to use wheels where possible

Since we need the raw Python to be available to add to the sys.path,
we extract the wheels before putting them in the tree.
However, you can't pip install an extracted wheel, so
install_pip_package() needed to be tweaked to "re-bundle" the wheel
before installing a vendored package.

sys.path configuration is adjusted for packages who had nested
their python files in their tar.gz artifacts.

Depends on D116511

Comment 2

[Mitchell Hentges [:mhentges] 🦀]

Attachment: Bug 1713377: Replace python packages with wheels where possible

This contains the vendoring changes caused by the
last patch.

For reviewing, there's a couple things to note:

• A bunch of files are deleted, since there's generally
  less files in a wheel than in a source archive.
• There's a new .dist.info directory for each
  extracted wheel, so expect roughly 5 or
  6 new files for each wheel'd package.
• There should be no source code changes other than
  moves from package names changing from having
  - to having _.

Depends on D116512

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/1537ac197686
Change vendoring to use wheels where possible r=ahal,glandium

Comment 4

[Atila Butkovits]

https://hg.mozilla.org/mozilla-central/rev/1537ac197686