gecko-dev/python
Nathan Froyd 9bd5c61497 Bug 1459721 - part 8 - pass full paths for IDL files to xpidl-process.py; r=chmanchester
The build system knows at build-backend time where to find each IDL
file; making xpidl-process.py rediscover this by requiring
xpidl-process.py to search through directories to find input IDL files
is silly.  To rememdy this, we're going to modify things so full paths
are passed into the script.  Those paths can then be used directly, with
no searching.
2018-05-15 10:05:23 -04:00
..
devtools/migrate-l10n
docs Bug 1448934 - Fix some spelling mistakes in locales/en-US r=flod 2018-04-24 10:26:35 +02:00
l10n/fluent_migrations Bug 1460806 - Clean up Fluent migration recipes r=gandalf 2018-05-11 08:12:52 +02:00
mach Bug 1453426 - Kill invoked process on keyboard interrupt in mach build. r=mshal 2018-04-17 15:30:27 -07:00
mozboot Bug 1352015 - Part 2: Build with Android O SDK. r=nalexander 2018-05-06 17:38:22 +02:00
mozbuild Bug 1459721 - part 8 - pass full paths for IDL files to xpidl-process.py; r=chmanchester 2018-05-15 10:05:23 -04:00
mozlint Bug 1460402 - Create a new class to manage pip install r=ahal 2018-05-10 19:05:30 +02:00
mozrelease Bug 1453274 - Bump mozrelease in tree version, to distinguish it from the pypi mirror version. r=rail 2018-04-24 21:55:22 -04:00
mozterm Bug 1434430 - [flake8] Fix blank 'except' statements r=rwood 2018-01-31 14:32:08 -05:00
mozversioncontrol
README
mach_commands.py Bug 1451501 - Fix error trying to run python-tests via |mach test|, r=gps,whimboo 2018-04-04 17:30:22 -04:00
moz.build Bug 1453274 - Add testing for python/mozrelease/versions.py r=rail 2018-04-23 12:40:26 -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