mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
gecko-dev/python
История
Tarek Ziadé 7c132a5e1b Bug 1668494 - add an influxdb layer r=sparky 
Differential Revision: https://phabricator.services.mozilla.com/D92480
 		2020-11-10 08:36:44 +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 1675306: Add mocks so Java-detection doesn't hit real file system r=firefox-build-system-reviewers,rstewart 2020-11-06 22:15:02 +00:00
mozbuild Bug 1670197: "Universal" python binaries shouldn't cause setup.py fails r=firefox-build-system-reviewers,rstewart 2020-11-09 18:00:58 +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 1668494 - add an influxdb layer r=sparky 2020-11-10 08:36:44 +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 Bug 1675707 - Allow not to activate the virtualenv when running mach python. r=firefox-build-system-reviewers,mhentges 2020-11-06 21:53:56 +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