1654663 - vendored glean_parser library should only be available to run_glean_parser

Status: RESOLVED FIXED

(Firefox Build System :: General, task)

Description

[Mitchell Hentges [:mhentges] 🦀]

When we implement Glean telemetry, we can't vendor the top-level Glean package (glean_sdk) because it has a native component - instead, we install it to the --user environment.
glean_sdk has associated dependencies, and one of them is glean_parser, which we already have vendored in-tree.

This is causing issues where, when we import glean_sdk, most dependencies are fetched from the --user pip environment, but (a very old) glean_parser is imported from in-tree.
There's only one consumer of the vendored glean_parser: run_glean_parser.py.

To solve this, we can:

1. Only use the vendored glean_parser library within run_glean_parser.py.
2. Grab all glean dependencies from the --user environment when importing Glean

Comment 1

[Mitchell Hentges [:mhentges] 🦀]

Attachment: Bug 1654663: Removes glean_parser from virtualenv_packages.txt

In preparation for Glean telemetry, we scope the availability of the out-of-date vendored
"glean_parser" library to its one usage: "run_glean_parser.py".

This allows Glean telemetry to load its modern "glean_parser" dependency from the
"--user" package environment.

Depends on D84566

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/aae7491870dd
Removes glean_parser from virtualenv_packages.txt r=firefox-build-system-reviewers,rstewart

Comment 3

[Narcis Beleuzu [:NarcisB]]

https://hg.mozilla.org/mozilla-central/rev/aae7491870dd