gecko-dev/python
Mike Conley 3da2d710da Bug 1688960 - Use h1 and h2 elements for panel headers and subheaders. r=Standard8,yzen,fluent-reviewers,flod
Differential Revision: https://phabricator.services.mozilla.com/D105081
2021-02-24 02:52:30 +00:00
..
devtools/migrate-l10n Bug 1654103: Standardize on Black for Python code in `mozilla-central`. 2020-10-26 18:34:53 +00:00
docs
gdbpp/gdbpp Bug 1654103: Standardize on Black for Python code in `mozilla-central`. 2020-10-26 18:34:53 +00:00
l10n Bug 1688960 - Use h1 and h2 elements for panel headers and subheaders. r=Standard8,yzen,fluent-reviewers,flod 2021-02-24 02:52:30 +00:00
lldbutils Bug 1654103: Standardize on Black for Python code in `mozilla-central`. 2020-10-26 18:34:53 +00:00
mach Bug 1678668: print sentry error report number on mach command failure r=firefox-build-system-reviewers,mhentges 2021-01-05 16:39:22 +00:00
mozboot Bug 1692940 - Don't bootstrap yasm. r=firefox-build-system-reviewers,dmajor 2021-02-23 01:26:47 +00:00
mozbuild Bug 1692575: Refactor the updatebot part of the moz.yaml schema to support multiple task types r=jewilde 2021-02-23 16:34:31 +00:00
mozlint Bug 1591991 Add lint Fixed count support to linters r=sylvestre 2021-02-08 19:00:10 +00:00
mozperftest Bug 1681669 - Add vision document for mozperftest. r=davehunt 2021-02-16 18:37:23 +00:00
mozrelease Bug 1648832: Make updater/Balrog support AArch64 macOS. r=aki 2020-11-13 18:41:56 +00:00
mozterm Bug 1680345 - python3 - Require six 1.13.0 in non third_party and non web-platform packages r=jgraham,jmaher 2020-12-03 22:54:35 +00:00
mozversioncontrol Backed out changeset 5153f0eaf518 (bug 1676533) as requested by glandium. CLOSED TREE 2020-12-02 07:58:47 +02:00
README
mach_commands.py Bug 1680802: Install pylint requirements with legacy resolver r=firefox-build-system-reviewers,sheehan,glandium 2021-01-05 20:14:25 +00:00
moz.build Bug 1654103: Standardize on Black for Python code in `mozilla-central`. 2020-10-26 18:34:53 +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