gecko-dev/python/devtools/migrate-l10n
Ricky Stewart 02a7b4ebdf Bug 1654103: Standardize on Black for Python code in mozilla-central.
Allow-list all Python code in tree for use with the black linter, and re-format all code in-tree accordingly.

To produce this patch I did all of the following:

1. Make changes to tools/lint/black.yml to remove include: stanza and update list of source extensions.

2. Run ./mach lint --linter black --fix

3. Make some ad-hoc manual updates to python/mozbuild/mozbuild/test/configure/test_configure.py -- it has some hard-coded line numbers that the reformat breaks.

4. Make some ad-hoc manual updates to `testing/marionette/client/setup.py`, `testing/marionette/harness/setup.py`, and `testing/firefox-ui/harness/setup.py`, which have hard-coded regexes that break after the reformat.

5. Add a set of exclusions to black.yml. These will be deleted in a follow-up bug (1672023).

# ignore-this-changeset

Differential Revision: https://phabricator.services.mozilla.com/D94045
2020-10-26 18:34:53 +00:00
..
migrate Bug 1654103: Standardize on Black for Python code in mozilla-central. 2020-10-26 18:34:53 +00:00
README.rst

devtools-l10n-migration script
==============================

For devtools.html, devtools will no longer rely on DTD files. This migration
script is aimed at localizers to automate the migration of strings from DTD to
properties files.

How to run this script?

To migrate all configuration files:
  python migrate/main.py path/to/your/l10n/repo/ -c migrate/conf/

To migrate only one configuration file:
  python migrate/main.py path/to/your/l10n/repo/ -c migrate/conf/bug1294186

All configuration files should be named after the bug where specific devtools strings were migrated.