gecko-dev/python
Wes Kocher 2458d6b297 Merge m-c to autoland, a=merge
MozReview-Commit-ID: KfZgcCxrZcg
2017-08-14 17:59:46 -07:00
..
devtools/migrate-l10n Bug 1346025 - Move vendored python modules from /python to /third_party/python, r=ted 2017-05-25 11:48:03 -04:00
mach Bug 1387307 - Add FailedCommandError to mach r=gps 2017-08-08 12:10:10 -07:00
mozboot Backed out changeset 514cf1f55c6f (bug 1380639) 2017-08-07 13:23:35 +02:00
mozbuild Merge m-c to autoland, a=merge 2017-08-14 17:59:46 -07:00
mozlint Bug 1387555 - [mozlint] Make use of quickfix when using --edit with vim/nvim, r=dylan 2017-08-09 10:03:02 -04:00
mozversioncontrol/mozversioncontrol Bug 1377216 - Use configure-derived VCS info to find repository; r=glandium 2017-07-18 15:46:47 -07:00
README Bug 1346025 - Move vendored python modules from /python to /third_party/python, r=ted 2017-05-25 11:48:03 -04:00
mach_commands.py Bug 1048446 - [python-test] Add 'sequential' key to python.ini manifests so tests can opt out of running in parallel, r=jmaher 2017-06-01 09:50:15 -04:00
moz.build Bug 1346025 - Move vendored python modules from /python to /third_party/python, r=ted 2017-05-25 11:48:03 -04: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