зеркало из https://github.com/mozilla/gecko-dev.git
a8db2a2c62
The way functions are being sandboxed in moz.configure land is that their global namespace is being replaced with a limited and identifiable dict. And we avoid re-wrapping a function that already received this treatment. The problem is that template functions have their global namespace replaced, and any function that is defined within the template inherits that global namespace. So when it comes time to wrap those functions defined in templates with e.g. depends, we detect that they're already wrapped although they are not, because we look if their global namespace is of the recognizable type we use when replacing it. So instead of looking at the global namespace type, keep track of all functions that are wrapped. |
||
|---|---|---|
| .. | ||
| PyECC | ||
| bitstring | ||
| blessings | ||
| compare-locales | ||
| configobj | ||
| eme | ||
| futures | ||
| jsmin | ||
| lldbutils | ||
| mach | ||
| mock-1.0.0 | ||
| mozboot | ||
| mozbuild | ||
| mozversioncontrol/mozversioncontrol | ||
| psutil | ||
| pyasn1 | ||
| pyasn1-modules | ||
| pystache | ||
| pyyaml | ||
| redo | ||
| requests | ||
| rsa | ||
| slugid | ||
| virtualenv | ||
| which | ||
| 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: * 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 ## pyyaml | pystache Used in taskcluster related mach commands to update download from github and remove .git and tests. Then run tests in taskcluster/tests/