mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
gecko-dev/python
История
Dzmitry Malyshau d2386f0411 Bug 1675851 - Add instant to allowed build dependencies r=mhoye 
Differential Revision: https://phabricator.services.mozilla.com/D96268
 		2020-11-12 17:52:04 +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 1565574 - Migrate protocol handler dialog strings to fluent. r=Gijs,flod 2020-10-29 13:44:01 +00:00
lldbutils Bug 1654103: Standardize on Black for Python code in `mozilla-central`. 2020-10-26 18:34:53 +00:00
mach Bug 1645423 - Sentry ignores errors caused by local changes r=mhentges 2020-11-03 19:22:51 +00:00
mozboot Bug 1676815 - Factorize Linux bootstrapping of Android builds r=andi DONTBUILD 2020-11-12 12:40:55 +00:00
mozbuild Bug 1675851 - Add instant to allowed build dependencies r=mhoye 2020-11-12 17:52:04 +00:00
mozlint Bug 1674923 - Pass down `virtualenv_manager` from `mach lint` down to linters r=ahal 2020-11-06 20:51:16 +00:00
mozperftest Bug 1675863 - mozperftest uses a fixed build of geckoview_example from 05/21/2020 r=sparky 2020-11-10 14:07:43 +00:00
mozrelease Bug 1654103: Standardize on Black for Python code in `mozilla-central`. 2020-10-26 18:34:53 +00:00
mozterm Bug 1654103: Standardize on Black for Python code in `mozilla-central`. 2020-10-26 18:34:53 +00:00
mozversioncontrol Bug 1654103: Standardize on Black for Python code in `mozilla-central`. 2020-10-26 18:34:53 +00:00
README
…
mach_commands.py Backed out 4 changesets (bug 1666347, bug 1667152, bug 1661624, bug 1666345) for causing mingw bustage. CLOSED TREE 2020-11-12 19:55:58 +02: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