mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
ae5ccc4eb3
It's not entirely clear passing down all the metadata makes sense. On the other hand, when creating the template execution sandbox, passing down exports does assign the value for the exported variable in that execution context. When that context is merged with the caller sandbox context, the exported variable is reassigned, even if the value is not modified. Then, if the caller sandbox itself reassigns the exported variable, it fails because calling a template already did it once, unexpectedly. Not passing down exported variables makes the template execution sandbox never set those exported variables, so that they are not merged back. The caller sandbox can then properly reassign the exported variable. |
||
|---|---|---|
| .. | ||
| blessings | ||
| codegen | ||
| configobj | ||
| jsmin | ||
| lldbutils | ||
| mach | ||
| mock-1.0.0 | ||
| mozboot | ||
| mozbuild | ||
| mozversioncontrol/mozversioncontrol | ||
| psutil | ||
| virtualenv | ||
| which | ||
| 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