Magic-Mirror/gecko-dev
1
0
Fork 0
mirror of https://github.com/mozilla/gecko-dev.git synced 2024-10-22 09:45:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
2d1e91425d
gecko-dev/python
History
Gregory Szorc 0ec82b74be Bug 1429342 - Ignore mach file-info arguments that don't resolve to paths; r=froydnj 
Without this, e.g. `mach file-info bugzilla-component build/does-not-exist`
reports the bug component is `Core :: Build Config`. Because paths
in CI have `build/` prefixes, people were typing `build/` paths into
`mach file-info` and reporting bugs against `Core :: Build Config`.

MozReview-Commit-ID: 8Zp6cnuw0Sh

--HG--
extra : rebase_source : 0b0e3d3247dc00681f62c5d43f8a1535f9f04738
2018-01-16 16:40:30 -08:00
..
devtools/migrate-l10n
l10n/fluent_migrations Bug 1411012 - Migrate a small chunk of Privacy pane in Preferences to Fluent. r=mshal,Pike 2017-11-09 12:11:32 -08:00
mach Bug 1415614 - Add an API to log all structured messages; r=mshal 2017-11-09 15:09:52 -08:00
mozboot Bug 1430933 - mozboot: Start with rustup 1.9.0. r=gps 2018-01-16 15:11:51 -08:00
mozbuild Bug 1429342 - Ignore mach file-info arguments that don't resolve to paths; r=froydnj 2018-01-16 16:40:30 -08:00
mozlint Bug 1422302 - Create python/mozterm for sharing terminal blessings across modules r=gps 2017-12-04 09:38:24 -05:00
mozterm Backed out 5 changesets (bug 1421799) for failing firefox ui functional tests. r=backout on a CLOSED TREE 2018-01-03 20:21:28 +02:00
mozversioncontrol Bug 1405588 - [mozversioncontrol] Use base_ref instead of upstream as default outgoing comparison on git, r=gps 2017-11-01 12:57:03 -04:00
mach_commands.py Bug 1403012 - Fix TypeError when running python unittests via |mach test|, r=gbrown 2018-01-12 11:22:58 -05:00
moz.build Backed out 2 changesets (bug 1403519) for bustage on \python\mozbuild\mozbuild\test\frontend\test_reader.py on a CLOSED TREE 2018-01-17 07:23:40 +02:00
README

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