зеркало из https://github.com/mozilla/gecko-dev.git
0912d6c960
The BuildReader's 'find_sphinx_variables' function is hardcoded to look for the SPHINX_TREES and SPHINX_PYTHON_PACKAGE_DIRS variables. But it's otherwise implemented to find any arbitrary variable (as long as they are a simple list or dict). This change simply moves the variable name(s) to the function call. The comment about possibly wanted to use a higher level AST library to parse other kinds of variables still applies, but for now this change is good enough to suit my needs. Differential Revision: https://phabricator.services.mozilla.com/D48424 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| docs | ||
| gdbpp/gdbpp | ||
| l10n | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| safety | ||
| README | ||
| mach_commands.py | ||
| moz.build | ||
README
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Vendored python modules (use third_party/python instead) * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243 https://bugzilla.mozilla.org/show_bug.cgi?id=1346025