view setup.cfg @ 5962:b68789e8c535

tests: spell out hg commands for readability

These are the abbreviations that are used just in a couple of places in the
tests. `hg d` is in my opinion an abbreviation of core command that everyone
should know, but I'd rather not use "unofficial" abbreviations in tests because
it takes a second to mentally expand what the command is when you're reading
it. In CLI when you type commands, it makes sense to abbreviate things to type
less. But tests are read much more often than they are written, so I'd like to
apply the same guidelines to them as to regular code: readability first.

Apart from readability, it's also consistency, because these particular
abbreviations are rare, and everywhere else the commands are spelled out.

[flake8]
ignore =
         #closing bracket does not match indentation of opening bracket's line
         E123,
         # closing bracket does not match visual indentation
         E124,
         # visually indented line with same indent as next logical line
         E129,
         # at least two spaces before inline comment
         E261,
         # too many leading '#' for block comment
         E266,
         # expected 2 blank lines, found 0
         E302,
         # expected 2 blank lines after end of function or class
         E305,
         # module level import not at top of file
         E402,
         # line too long (82 > 79 characters)
         E501,
         # do not assign a lambda expression, use a def
         E731,
         # class names should use CapWords convention
         N801,
         # line break occurred before a binary operator
         W503
builtins=xrange, execfile