gecko/python
Gregory Szorc 461b5aef7e Bug 774572 - Part 2: Define JAR_MANIFESTS in moz.build files; r=glandium
Every directory with a jar.mn now has JAR_MANIFESTS defined in its
moz.build file.

We also removed the may_skip special consideration of jar.mn files
because this information is now available during tier traversal by the
reader courtesy of the variables being present in moz.build files.

--HG--
extra : rebase_source : 21049b15e6bd9cf65b0805ccaccc4ba5aae93c98
extra : amend_source : 0b1ea866d725beef92d37c6f6d475369ac002e19
2013-12-10 16:18:11 +09:00
..
blessings
codegen
configobj
mach Bug 942275 - Add support for setuptools' entry points to mach, r=gps 2013-12-06 09:24:09 -05:00
mock-1.0.0
mozboot Bug 943874 - Update Git URL printed during mach bootstrap; r=ehsan 2013-11-28 13:03:04 +07:00
mozbuild Bug 774572 - Part 2: Define JAR_MANIFESTS in moz.build files; r=glandium 2013-12-10 16:18:11 +09:00
mozversioncontrol/mozversioncontrol Bug 941833 - mach mercurial-setup should define host fingerprints during repo operations; r=nalexander 2013-11-21 12:19:32 -08:00
psutil
virtualenv Bug 914500 - Upgrade virtualenv to 1.10.1; r=mshal 2013-09-10 17:07:12 -07:00
which
mach_commands.py
Makefile.in Bug 585016 - Move buildlist.py to a mozbuild action; r=mshal 2013-10-11 07:22:49 -07:00
moz.build Bug 939367 - Allow Sphinx docs to come from all over the tree; r=glandium 2013-11-20 12:37:22 -08: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