gecko-dev/python
Jim Chen c3c2bfc408 Bug 1378410 - 2a. Expose `set` to moz.build sandbox; r=gps
To construct an empty set, we need to use the `set()` notation. In order
to do that, we need to expose `set` to the moz.build sandbox.

MozReview-Commit-ID: DMyKnF0FEx2

--HG--
extra : rebase_source : 5cfe8080ec333a1eca70cd3edba2aaaff6406820
2017-09-01 14:02:30 -04: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 1289444 - Forward extra arguments in |mach test| to the underlying test commands, r=chmanchester 2017-08-29 16:20:47 -04:00
mozboot Bug 1395768 - Use absolute path to mach. r=gps 2017-09-01 03:15:45 +03:00
mozbuild Bug 1378410 - 2a. Expose `set` to moz.build sandbox; r=gps 2017-09-01 14:02:30 -04:00
mozlint Bug 1395126 - Support cascading configuration for flake8, r=bc 2017-08-29 17:32:31 -04:00
mozversioncontrol/mozversioncontrol Bug 1393242 - Use hglib for get_files_in_working_directory(); r=mshal 2017-08-23 15:21:16 -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 1339178 - Use pytest to run python-tests, r=davehunt 2017-08-29 14:50:33 -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