gecko-dev/python
Chris Manchester 399d530b9b Bug 1556185 - Ensure autoconf.mk is tracked as a dependency when preprocessing webidls. r=nalexander
webidlsrcs.mk is treated specially by the build system, and this entire
process should be supported better by moz.build, but in the meantime this
fixes the clobber bug caused by not re-building these targets when defines
are updated.

Differential Revision: https://phabricator.services.mozilla.com/D33415

--HG--
extra : moz-landing-system : lando
2019-06-03 20:33:36 +00:00
..
devtools/migrate-l10n
docs Bug 1490253 - Update documentation on vendoring Python packages based on switch to pip-tools; r=ahal 2018-10-15 13:36:30 +00:00
l10n Bug 1549561 - Migrate strings from pipnss.properties to aboutCertError.ftl. r=flod CLOSED TREE 2019-05-30 09:43:23 +03:00
mach Bug 1521996 - Part 1: Add `conditional_name` to mach @Command definition. r=ahal 2019-05-17 21:39:31 +00:00
mozboot Bug 1556257 - Add Funtoo support to mach bootstrap. r=froydnj 2019-06-03 01:15:09 +00:00
mozbuild Bug 1556185 - Ensure autoconf.mk is tracked as a dependency when preprocessing webidls. r=nalexander 2019-06-03 20:33:36 +00:00
mozlint Bug 1552897 - Ride along: format with black r=ahal 2019-05-23 16:44:04 +00:00
mozrelease Bug 1549889: Add support for displaying WNP conditionally on build-id; r=nthomas 2019-05-29 23:47:07 +00:00
mozterm Bug 1471171 - Indicate that mozterm is universal and works on any version of Python; r=emorley 2018-07-02 12:03:10 +01:00
mozversioncontrol Bug 1520309: Set HGPLAIN env var when running hg push-to-try; r=ahal 2019-04-09 21:10:49 +00:00
safety Bug 1476003 Update python virtual environment for |mach python-safety| r=davehunt 2018-07-16 15:36:50 +00:00
README
mach_commands.py Bug 1504308 - [mach] Pass path to Python interpreter to python-tests. r=ahal 2019-04-03 21:02:55 +00:00
moz.build Bug 1547730 - Set python test annotations to correspond to currently-passing py3 tests r=glandium 2019-05-28 14:28: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