gecko/python
Gregory Szorc 2a4aace69a Bug 1058036 - Ensure dependency isn't lost when ORing InstallManifest; r=glandium
The install manifest processor starts with an empty InstallManifest and
uses |= to "concatenate" instances. It became pretty obvious when
developing some patches that add more preprocessed files to install
manifests that the source install manifest dependency was getting
lost during the |= operation. This patch fixes it.

The solution is not ideal performance wise. But slightly worse
performance (only after config.status, however) is better than
clobbers.

A test has been added to ensure this doesn't regress.

--HG--
extra : rebase_source : 848aebbbc935ce2bca2d3fcc85d1df534e734e0d
2014-08-24 20:19:55 -04:00
..
blessings
codegen
configobj
jsmin
lldbutils Bug 1002712 - Add lldb type summaries for rects and regions. r=heycam 2014-04-29 12:14:42 +02:00
mach Bug 1051987 - Remove useless option which wasn't supposed to go in the commit 2014-08-18 15:33:51 +02:00
mock-1.0.0
mozboot Merge mozilla-central to mozilla-inbound on a CLOSED TREE 2014-07-28 16:30:30 +02:00
mozbuild Bug 1058036 - Ensure dependency isn't lost when ORing InstallManifest; r=glandium 2014-08-24 20:19:55 -04:00
mozversioncontrol/mozversioncontrol Bug 1033656 - Add reviewboard to mach mercurial-setup; version checking; r=smacleod 2014-07-02 14:05:42 -07:00
psutil
virtualenv Bug 995374 - Update virtualenv to 1.11.4; r=mshal 2014-04-11 12:07:20 -07:00
which
mach_commands.py Bug 952280 - mach python commands now use virtualenv APIs; r=mshal 2013-12-19 13:48:37 -08:00
moz.build Bug 1053140 part 3 - Separate out sandbox infrastructure from moz.build variables storage. r=gps 2014-08-15 13:52:18 +09:00
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