gecko-dev/testing/mozbase
Andrew Halberstadt 57887f2601 Bug 1328830 - [manifestparser] Check line continuation before looking for next key, r=jmaher
Currently manifestparser will only look for line continuations *after* looking for a key. This means
that line continuations cannot contain key separators. For example, this:

    [test]
    foo=
      bar=baz

gets treated as:

    {'name': 'test', 'foo': '', 'bar': 'baz'}

Here, bar=baz will be treated as a new key/value pair despite the indentation. This patch switches
the order around, so we look for a continuation first. Now, it is only treated as a continuation if
the indent is greater than the indent of the preceding key.

So this manifest:

    [test]
    foo=bar
      baz=fleem

is a continuation and results in:

    {'name': 'test', 'foo': 'bar\nbaz=fleem'}

But this manifest:

    [test]
      foo=bar
      baz=fleem

is not a continuation, and yields:

    {'name': 'test', 'foo': 'bar', 'baz': 'fleem'}

MozReview-Commit-ID: FAMP5TUIo9q

--HG--
extra : rebase_source : 624c53cfe0565374c1224dd86a3fffc8831279d3
2017-07-19 14:48:01 -04:00
..
docs Bug 1373294 - Fix E305 (two blank lines after method or class) in files enabled by flake8 linter, r=jmaher 2017-06-15 12:10:59 -04:00
manifestparser Bug 1328830 - [manifestparser] Check line continuation before looking for next key, r=jmaher 2017-07-19 14:48:01 -04:00
mozcrash Bug 1373294 - Fix E305 (two blank lines after method or class) in files enabled by flake8 linter, r=jmaher 2017-06-15 12:10:59 -04:00
mozdebug
mozdevice Bug 1373294 - Fix E305 (two blank lines after method or class) in files enabled by flake8 linter, r=jmaher 2017-06-15 12:10:59 -04:00
mozfile Bug 1373294 - Fix E305 (two blank lines after method or class) in files enabled by flake8 linter, r=jmaher 2017-06-15 12:10:59 -04:00
mozhttpd Bug 1373294 - Fix E305 (two blank lines after method or class) in files enabled by flake8 linter, r=jmaher 2017-06-15 12:10:59 -04:00
mozinfo Bug 1373294 - Fix E305 (two blank lines after method or class) in files enabled by flake8 linter, r=jmaher 2017-06-15 12:10:59 -04:00
mozinstall Bug 1048446 - [mozinstall] Add ability to download and extract installer from a url, r=whimboo 2017-03-09 12:20:03 -05:00
mozleak
mozlog Bug 1349516 - Add support to pytest-mozlog for tests rerun using pytest-rerunfailures; r=ahal 2017-07-20 18:03:11 +01:00
moznetwork
mozprocess Bug 1378712 - Remove all trailing whitespaces r=Ehsan 2017-07-06 14:00:35 +02:00
mozprofile Bug 1377510 - Add the ability to install webextensions with mozprofile r=automatedtester 2017-07-24 12:08:53 +02:00
mozrunner Backed out changeset 32f1daf0a256 (bug 1372263) for crashing in mochitests dom/ipc/tests/test_CrashService_crash.html and dom/ipc/tests/test_process_error.xul with js::ctypes::ConvertToJS. r=backout on a CLOSED TREE 2017-07-01 00:37:33 +02:00
mozscreenshot
mozsystemmonitor
moztest Bug 1373294 - Fix E305 (two blank lines after method or class) in files enabled by flake8 linter, r=jmaher 2017-06-15 12:10:59 -04:00
mozversion Bug 1373294 - Fix E305 (two blank lines after method or class) in files enabled by flake8 linter, r=jmaher 2017-06-15 12:10:59 -04:00
moz.build Bug 1373294 - Fix E305 (two blank lines after method or class) in files enabled by flake8 linter, r=jmaher 2017-06-15 12:10:59 -04:00
packages.txt Bug 1347483 - blessings package should not be downloaded during mach virtualenv setup; r=mshal 2017-03-22 14:26:18 -04:00
README.md
setup_development.py Bug 1373294 - Fix E305 (two blank lines after method or class) in files enabled by flake8 linter, r=jmaher 2017-06-15 12:10:59 -04:00
versioninfo.py

Mozbase

Mozbase is a set of easy-to-use Python packages forming a supplemental standard library for Mozilla. It provides consistency and reduces redundancy in automation and other system-level software. All of Mozilla's test harnesses use mozbase to some degree, including Talos, mochitest, reftest, Autophone, and Eideticker.

Learn more about mozbase at the project page.

Read detailed docs online, or build them locally by running "make html" in the docs directory.

Consult open bugs and feel free to file new bugs.