gecko-dev/python
Geoff Brown 9e59579c39 Bug 1601076 - Fix some broken BUG_COMPONENTS in moz.build files; r=jmaher
Some of these were obvious typos. Others probably reflect once-correct components
that have been combined, split, or otherwise obsoleted; for these I've tried to
use the component associated with the bugs for recent changes to the affected files.

Differential Revision: https://phabricator.services.mozilla.com/D55756

--HG--
extra : moz-landing-system : lando
2019-12-04 13:55:45 +00:00
..
devtools/migrate-l10n
docs
gdbpp/gdbpp
l10n Bug 1600560 - Remove Fluent migration recipes for Firefox 71 r=Pike 2019-12-02 10:12:39 +00:00
mach Bug 1581224 - convert mach uuid to be compatible with both python2/3 r=Callek 2019-10-21 16:33:00 +00:00
mozboot Backed out 3 changesets (bug 1595218) for Windows wrench failures. 2019-12-04 05:49:06 +02:00
mozbuild Backed out 3 changesets (bug 1595218) for Windows wrench failures. 2019-12-04 05:49:06 +02:00
mozlint Bug 1589056 - [mozlog] Update mozlog version number to 5.0 r=jgraham 2019-10-24 14:12:32 +00:00
mozrelease Bug 1595632 - don't hardcode TC root url for release start emails, r=Callek 2019-11-14 03:15:51 +00:00
mozterm
mozversioncontrol Bug 1592855 - run mach vendor python with python3 r=ahal 2019-11-05 15:29:44 +00:00
safety Bug 1591220 - migrate python-safety to run with python3 by default r=ahal 2019-11-04 21:55:21 +00:00
README
mach_commands.py Backed out changeset 3034ec8681ac (bug 1590745) for breaking local macOS 10.15 builds (bug 1600720). a=backout 2019-12-03 19:06:29 +01:00
moz.build Bug 1601076 - Fix some broken BUG_COMPONENTS in moz.build files; r=jmaher 2019-12-04 13:55:45 +00: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:

* 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